CVSS 4.0
4.8 mediumCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NMedium (4.8) in musl libc. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:LExplain CVE-2026-6042 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-6042?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-6042?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-6042 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| musl libc | 1.2.0 |
| musl libc | 1.2.1 |
| musl libc | 1.2.2 |
| musl libc | 1.2.3 |
| musl libc | 1.2.4 |
| musl libc | 1.2.5 |
| musl libc | 1.2.6 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | musl | no fix listed | DEBIAN-CVE-2026-6042 |
| Debian | 13 | musl | 1.2.5-3.1~deb13u1 | DEBIAN-CVE-2026-6042 |
| Debian | 14 | musl | 1.2.5-3.1 | DEBIAN-CVE-2026-6042 |
| Ubuntu | 22.04:LTS, 24.04:LTS, 25.10 and 6 more | musl | no fix listed | UBUNTU-CVE-2026-6042 |
| Alpine | v3.19 | musl | 1.2.4_git20230717-r6 | ALPINE-CVE-2026-6042 |
| Alpine | v3.20 | musl | 1.2.5-r2 | ALPINE-CVE-2026-6042 |
| Alpine | v3.21 | musl | 1.2.5-r10 | ALPINE-CVE-2026-6042 |
| Alpine | v3.22 | musl | 1.2.5-r11 | ALPINE-CVE-2026-6042 |
| Alpine | v3.23 | musl | 1.2.5-r22 | ALPINE-CVE-2026-6042 |
| Alpine | v3.24 | musl | 1.2.6-r1 | ALPINE-CVE-2026-6042 |
| Alpaquita | 23 | musl-default | 1.2.4-r14 | BELL-CVE-2026-6042 |
| Alpaquita | 23 | musl-perf | 1.2.4-r10 | BELL-CVE-2026-6042 |
| Alpaquita | 25 | musl-default | 1.2.5-r15 | BELL-CVE-2026-6042 |
| Alpaquita | 25 | musl-perf | 1.2.5-r16 | BELL-CVE-2026-6042 |
| Alpaquita | stream | musl-perf, musl-default | 1.2.6-r2 | BELL-CVE-2026-6042 |
| BellSoft Hardened Containers | 23 | musl-default | 1.2.4-r14 | BELL-CVE-2026-6042 |
| BellSoft Hardened Containers | 23 | musl-perf | 1.2.4-r10 | BELL-CVE-2026-6042 |
| BellSoft Hardened Containers | 25 | musl-default | 1.2.5-r15 | BELL-CVE-2026-6042 |
| BellSoft Hardened Containers | 25 | musl-perf | 1.2.5-r16 | BELL-CVE-2026-6042 |
| BellSoft Hardened Containers | stream | musl-perf, musl-default | 1.2.6-r2 | BELL-CVE-2026-6042 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpine · Alpaquita · BellSoft Hardened Containers.
Red Hat rates this Moderate.
A MODERATE flaw in musl libc's `iconv` function, specifically within the GB18030 4-byte Decoder, allows a local attacker to trigger a Denial of Service. This vulnerability arises from inefficient algorithmic complexity when processing specific manipulations. Red Hat Enterprise Linux does not use musl libc as its default C library, limiting direct impact to environments or applications that explicitly utilize musl libc.
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-6042.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.