CVE-2024-25255: Command Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 12:54 UTC
- EPSS
- 1.4% chance of exploitation in 30 days – higher than 73% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Given the lack of official patches, organizations should implement immediate compensating controls. First, restrict network access to systems running Sublime Text 4, especially limiting exposure to untrusted networks. Employ application whitelisting and endpoint detection and response (EDR) solutions to monitor and block suspicious command execution originating from Sublime Text processes. Disable or restrict the use of the New Build System module if possible, or configure it to accept only trusted build scripts. Conduct thorough code reviews and audits of build configurations to detect potentially malicious commands. Use containerization or sandboxing to isolate development environments, minimizing the impact of any exploitation. Maintain strict access controls and ensure systems running Sublime Text are updated to the latest versions once patches become available. Educate developers and system administrators about the risks and signs of exploitation. Finally, monitor logs for unusual command execution patterns and prepare incident response plans tailored to this vulnerability.
Description
Sublime Text 4 was discovered to contain a command injection vulnerability via the New Build System module. NOTE: multiple third parties report that this is intended behavior.