CVSS 3.1
2.5 lowCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:NLow (2.5) in gnu libidn. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:NExplain CVE-2026-57053 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-57053?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-57053?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-57053 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 |
|---|---|
| GNU libidn | before 1.44 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | libidn | no fix listed | DEBIAN-CVE-2026-57053 |
| Debian | 14 | libidn | 1.44-1 | DEBIAN-CVE-2026-57053 |
| Ubuntu | 14.04:LTS, 16.04:LTS, 18.04:LTS and 2 more | libidn | no fix listed | UBUNTU-CVE-2026-57053 |
| Ubuntu | 22.04:LTS | libidn | 1.38-4ubuntu1.1 | UBUNTU-CVE-2026-57053 USN-8521-1 |
| Ubuntu | 24.04:LTS | libidn | 1.42-1ubuntu0.1 | UBUNTU-CVE-2026-57053 USN-8521-1 |
| Ubuntu | 26.04:LTS | libidn | 1.43-2ubuntu0.26.04.1 | UBUNTU-CVE-2026-57053 USN-8521-1 |
| Red Hat | hummingbird:1 | idn2, libidn2, libidn2-devel | 0:2.3.8-4.hum1 | RHSA-2026:42125 |
| SUSE | Linux Enterprise Module for Basesystem 15 SP7 | libidn | 1.34-150000.3.5.1 | SUSE-SU-2026:4000-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | libidn | 1.43-160000.3.1 | SUSE-SU-2026:23621-1 |
| SUSE | Linux Enterprise Server LTSS Extended Security 12 SP5 | libidn | 1.28-5.9.1 | SUSE-SU-2026:4081-1 |
| openSUSE | Leap 16.0 | libidn | 1.43-160000.3.1 | openSUSE-SU-2026:21758-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE.
Red Hat rates this Moderate.
This flaw resides in GNU libidn's idna_to_unicode_internal() function, used by the idna_to_unicode_* API family. The function assumes its internal ToASCII comparison buffer always begins with the "xn--" ACE prefix. When a decoded label is pure ASCII and shorter than four characters, no prefix is added, and the round-trip verification instead reads past the buffer's null terminator into uninitialized stack memory. Under certain call sequences that leave matching residual data on the stack, this allows an ACE-encoded label that should fail validation to be silently accepted and normalized to a different, shorter string, which could affect domain-based security decisions (allow/deny-list matching, hostname comparisons, routing, logging) made by applications relying on the result.
This flaw does not affect libidn2. Its round-trip verification in lookup.c never assumes the "xn--" prefix is present on caller-supplied data; every prefix-relative offset is either guarded by an explicit prefix check beforehand or applied to a buffer the function itself just wrote the prefix into, and it compares the full label rather than a bare suffix.
No configuration-level mitigation is available; triggering the incorrect result depends on uninitialized stack content from earlier processing, so behavior is non-deterministic and cannot be reliably suppressed via input filtering. Users should update to a fixed libidn package once available. Applications that must process untrusted internationalized domain names before a fix is available should treat output of idna_to_unicode_8z8z()/idna_to_unicode_8zlz() as unverified, perform an independent comparison against the original ACE-encoded input, or use libidn2 for IDNA processing, which is not affected.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | libidn2-main-2.3.8-4.hum1 | Fixed 2026-07-20 | RHSA-2026:42125 |
| Migration Toolkit for Containers | libidn | Fix deferred | |
| Red Hat Enterprise Linux 10 | libidn2 | Not affected | |
| Red Hat Enterprise Linux 6 | libidn | Out of support scope | |
| Red Hat Enterprise Linux 7 | libidn | Fix deferred | |
| Red Hat Enterprise Linux 8 | libidn | Fix deferred | |
| Red Hat Enterprise Linux 8 | libidn2 | Not affected | |
| Red Hat Enterprise Linux 9 | libidn2 | Not affected |
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-57053.