# CVE-2025-65741: Code injection in n/a

> An attacker can execute arbitrary code by injecting a malicious dynamic library into Sublime Text on macOS.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-vq8r-x7fq-6487

## What is CVE-2025-65741?

CVE-2025-65741 is a critical code injection vulnerability in n/a, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2025-65741?

It affects 1 product.


Products: Sublimetext Sublime Text 3.

## How do I fix CVE-2025-65741?

No fix has been published for CVE-2025-65741 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-65741 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65741 exists.

Public exploit code:

- https://github.com/vinicius-batistella/CVE-2025-65741 (github_poc): https://github.com/vinicius-batistella/CVE-2025-65741

## Other vulnerabilities in n/a

- [CVE-2019-9116](https://insights.sbomify.com/CVE-2019-9116/): Other in n/a (high 7.8)
- [CVE-2017-8368](https://insights.sbomify.com/CVE-2017-8368/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-65741 and fix it if it is affected.

What it is: CVE-2025-65741 is a critical code injection vulnerability in n/a, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65741 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-65741/ (Markdown: https://insights.sbomify.com/CVE-2025-65741/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-65741
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-65741
- OSV: https://osv.dev/vulnerability/CVE-2025-65741

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-65741/
Summaries are generated and may contain mistakes; the official description above is the record.