Security readout for executives and security teams
Plain-English summary
CVE-2017-8368 is a reported Sublime Text 3 Build 3126 issue where a crafted .mkv file can crash the editor or possibly cause other unspecified impact after user interaction. The public record does not provide a CVSS score, confirmed patch, or evidence of active exploitation.
Executive priority
Treat this as a workstation hygiene issue, not an internet-facing emergency. Prioritize if teams routinely inspect untrusted files in Sublime Text or if legacy Sublime Text builds remain unmanaged.
Technical view
The CVE describes a user-assisted flaw triggered by an untrusted crafted .mkv file and subsequent user-defined editor commands. The demonstrated impact is denial of service; other impact is not specified. Public affected-product metadata is incomplete, though the description names Sublime Text 3 Build 3126.
Likely exposure
Exposure is most likely on developer or analyst workstations running Sublime Text 3 Build 3126 and opening untrusted media-like files as text. Server-side exposure is not indicated by the provided sources.
Exploitation context
The provided sources describe a victim obtaining a crafted file from a remote location and interacting with it in Sublime Text. The CVE is not listed as KEV, and the bundle provides no evidence of active exploitation.
Researcher notes
The record lacks CVSS, CWE, precise root cause, and confirmed remediation details. The description supports user-assisted denial of service and only says possible unspecified other impact, so avoid assuming code execution or broad product exposure.
Mitigation direction
- Inventory Sublime Text installations and identify Build 3126 usage.
- Avoid opening untrusted .mkv files in Sublime Text.
- Check Sublime Text vendor guidance or issue history for fixed builds.
- Upgrade Sublime Text where a vendor-supported fixed version is available.
- Use endpoint controls to quarantine suspicious downloaded files.
Validation and detection
- Confirm whether Sublime Text 3 Build 3126 exists in managed endpoints.
- Review file association policies for .mkv and text editors.
- Check endpoint telemetry for crashes linked to untrusted downloaded files.
- Verify whether users handling untrusted files use isolated analysis environments.
- Document uncertainty because public severity and fix data are incomplete.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-8368 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/SublimeTextIssues/Core/issues/1700CVE reference · x_refsource_CONFIRM
- https://github.com/wlinzi/security_advisories/tree/master/CVE-2017-8368CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.