dbcve.org
Sublime Text 3Application · Sublimetext

CVE-2025-65741

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 3.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Sublime Text 3 Build 3208 and prior for macOS is vulnerable to dynamic library injection (Dylib Injection). An attacker can compile a malicious .dylib file and force its execution within the Sublime Text application process context, achieving arbitrary code execution with the privileges of the Sublime Text user. This is a code execution vulnerability specific to the macOS platform.

MitigationApply vendor-supplied patch/updates for Sublime Text 3 to a build newer than 3208. Until patch is available, restrict file system permissions around Sublime Text installation directories and monitor for unauthorized .dylib files in application paths.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sublime Text 3Application
Affected:< 3.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify macOS platform
    Run 'uname -s' or check System Preferences to confirm the operating system is macOS. This vulnerability only affects macOS systems.
    Affected if The system is not running macOS - the vulnerability does not apply to Windows or Linux.
  2. Confirm Sublime Text 3 is installed
    Check for the application at /Applications/Sublime Text.app or run 'ls /Applications | grep -i sublime'
    Affected if Sublime Text 3 is not installed on the system.
  3. Check installed Sublime Text 3 version
    Run 'defaults read /Applications/Sublime\ Text.app/Contents/Info.plist CFBundleVersion' or right-click the app, select Get Info, and check the Version field
    Affected if The installed version is 3.2.2 or higher (or build number > 3208). Versions prior to 3.2.2 or build 3208 and earlier are affected.
  4. Check for suspicious dylib files in application path
    Run 'ls -la /Applications/Sublime\ Text.app/Contents/Frameworks/' and inspect for any unexpected .dylib files that may have been injected
    Affected if Unexpected or unauthorized .dylib files exist in the application Frameworks directory, indicating potential injection.

You are affected if running macOS with Sublime Text 3 version less than 3.2.2 (or build 3208 or earlier) installed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.2.2 or later
Fixed in 3.2.2
Interim mitigation

Apply vendor-supplied patch/updates for Sublime Text 3 to a build newer than 3208. Until patch is available, restrict file system permissions around Sublime Text installation directories and monitor for unauthorized .dylib files in application paths.

Recommended fix High confidence

Sublime Text 3.2.2 or later (Build 3211+)

  1. Download Sublime Text 3.2.2 or later from the official Sublime Text website (www.sublimetext.com)
  2. Close any running instances of Sublime Text 3
  3. Install the downloaded version, which will overwrite the vulnerable installation
  4. Launch Sublime Text and verify the application runs normally
  5. Confirm the version by going to 'Sublime Text' > 'About Sublime Text' and verifying the build number is greater than 3208
Caveat Minor: User settings and packages typically persist across upgrades, though it's recommended to back up the ~/Library/Application Support/Sublime Text 3 folder before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sublime Text 3 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65741 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-65741 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data