# CVE-2025-26519: Memory corruption in musl

> An out-of-bounds write in musl libc allows attackers to execute code or cause denial of service via crafted EUC-KR text conversion.

- **Severity:** High 8.1 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Feb 2025
- **Updated:** 14 Feb 2025
- **Also known as:** ALPINE-CVE-2025-26519, BELL-CVE-2025-26519, DEBIAN-CVE-2025-26519, GHSA-xpv5-92cc-8f65, OESA-2025-1252, OESA-2025-1253, OESA-2025-1254, OESA-2025-1255, ROOT-OS-ALPINE-315-CVE-2025-26519, UBUNTU-CVE-2025-26519

## What is CVE-2025-26519?

CVE-2025-26519 is a high-severity memory corruption vulnerability in musl-libc musl, published on 14 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

musl libc 0.9.13 through 1.2.5 before 1.2.6 has an out-of-bounds write vulnerability when an attacker can trigger iconv conversion of untrusted EUC-KR text to UTF-8.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Musl-Libc Musl.

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

Upgrade to a fixed version.

## Is CVE-2025-26519 being exploited?

There is no known exploitation of CVE-2025-26519 in the wild and no public exploit code.

## Other vulnerabilities in musl-libc musl

- [CVE-2014-3484](https://insights.sbomify.com/CVE-2014-3484/): Memory corruption in musl libc (critical 9.8)
- [CVE-2019-14697](https://insights.sbomify.com/CVE-2019-14697/): Memory corruption in n/a (critical 9.8)
- [CVE-2015-1817](https://insights.sbomify.com/CVE-2015-1817/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-15650](https://insights.sbomify.com/CVE-2017-15650/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26519 is a high-severity memory corruption vulnerability in musl-libc musl, published on 14 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26519 in the wild and no public exploit code.

Affected product: musl-libc musl. 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-26519/ (Markdown: https://insights.sbomify.com/CVE-2025-26519/index.md)
```

## Sources

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

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