# CVE-2024-25262: Memory corruption in n/a

> Attackers can cause a denial of service by supplying a crafted TTF file to the texlive-bin component, requiring a patch to mitigate the heap buffer overflow.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Feb 2024
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-25262, GHSA-79qr-9mf7-fr3g, OESA-2026-2110, OESA-2026-2111, OESA-2026-2112, OESA-2026-2113, OESA-2026-2114, UBUNTU-CVE-2024-25262

## What is CVE-2024-25262?

CVE-2024-25262 is a high-severity memory corruption vulnerability in n/a, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

texlive-bin commit c515e was discovered to contain heap buffer overflow via the function ttfLoadHDMX:ttfdump. This vulnerability allows attackers to cause a Denial of Service (DoS) via supplying a crafted TTF file.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2024-25262?


## How do I fix CVE-2024-25262?

Apply the vendor's patch.

## Is CVE-2024-25262 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-25262 and fix it if it is affected.

What it is: CVE-2024-25262 is a high-severity memory corruption vulnerability in n/a, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25262 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-2024-25262/ (Markdown: https://insights.sbomify.com/CVE-2024-25262/index.md)
```

## Sources

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

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