CVE-2025-26519

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.

Published: 2025-02-14 Last update: 2025-12-10 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-26519 is rated Low Risk (33.4/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-26519

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.07% 0.02% -0.06%
2 2025-11-18 0.04% 0.07% +0.03%
3 2025-02-14 0.04%

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-26519

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.1 HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
1.4 6.0 [email protected]
7.0 3.1 HIGH
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.0 5.9 [email protected]

Weakness enumeration for CVE-2025-26519

OS Trackers for CVE-2025-26519

vendor priority summary link
alpine CVE-2025-26519: 1 source package rows (musl); 49 state rows across 7 repos (3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 29, open 20. https://security.alpinelinux.org/vuln/CVE-2025-26519
debian not yet assigned CVE-2025-26519 not yet assigned priority: Debian including 1 source packages (musl), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2025-26519
ubuntu medium CVE-2025-26519 medium priority: Ubuntu including 1 source packages (musl), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 8, ignored 2. https://ubuntu.com/security/CVE-2025-26519

Affected software / configurations for CVE-2025-26519

Vendor Product Version Raw CPE
musl-libc musl >= 0.9.13, < 1.2.6 cpe:2.3:a:musl-libc:musl:*:*:*:*:*:*:*:*

References for CVE-2025-26519

URL Tags
https://git.musl-libc.org/cgit/musl/commit/?id=c47ad25ea3b484e10326f933e927c0bc8cded3da Patch
https://git.musl-libc.org/cgit/musl/commit/?id=e5adcd97b5196e29991b524237381a0202a60659 Patch
https://www.openwall.com/lists/oss-security/2025/02/13/2 Mailing List Mitigation Third Party Advisory
http://www.openwall.com/lists/oss-security/2025/02/13/2 Mailing List Mitigation Third Party Advisory
http://www.openwall.com/lists/oss-security/2025/02/13/3 Mailing List Third Party Advisory
http://www.openwall.com/lists/oss-security/2025/02/13/4 Mailing List Mitigation Third Party Advisory
http://www.openwall.com/lists/oss-security/2025/02/13/5 Mailing List Mitigation Third Party Advisory
http://www.openwall.com/lists/oss-security/2025/02/14/5 Mailing List Third Party Advisory
http://www.openwall.com/lists/oss-security/2025/02/14/6 Mailing List Third Party Advisory
cvelogic Threat Intelligence