Skip to main content
VulnerabilityPublished Updated

CVE-2025-65741: Uncontrolled Search Path Element

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

  1. Immediately monitor Sublime Text official channels for patches addressing CVE-2025-65741 and apply updates as soon as they become available.
  2. Until a patch is released, restrict the execution of untrusted or unsigned dylibs on macOS systems using tools like Gatekeeper and System Integrity Protection (SIP).
  3. Employ macOS hardened runtime and code signing enforcement to prevent unauthorized dylib injection.
  4. Limit Sublime Text usage to trusted environments and avoid opening untrusted projects or files that could trigger dylib loading.
  5. Use endpoint detection and response (EDR) solutions capable of detecting anomalous dylib injection or process manipulation behaviors.
  6. Educate developers and users about the risks of loading unverified plugins or extensions in Sublime Text.
  7. Implement network segmentation and strict access controls to reduce the attack surface and prevent remote delivery of malicious dylibs.
  8. Regularly audit macOS systems for unauthorized dylibs loaded into critical applications.
  9. Consider temporary use of alternative editors or IDEs on macOS until the vulnerability is fully mitigated.

Description

Sublime Text 3 Build 3208 or prior for MacOS is vulnerable to Dylib Injection. An attacker could compile a .dylib file and force the execution of this library in the context of the Sublime Text application.

References

Community reviews

Loading reviews…