IDN result corruption via unchecked prefix offset
Published Jun 23, 2026 · Updated Jun 23, 2026
Out-of-bounds reads in GNU Libidn before 1.44 allow local users to alter IDN conversion results via crafted Punycode labels. In idna_to_unicode_internal, round-trip verification skips four bytes of a re-encoded label without confirming that the xn-- prefix is present. Exploitation depends on stack layout and an application passing attacker-controlled labels to a ToUnicode API; outcomes include invalid-label acceptance or a process crash.
Summary
What happened
Out-of-bounds reads in GNU Libidn before 1.44 allow local users to alter IDN conversion results via crafted Punycode labels. In idna_to_unicode_internal, round-trip verification skips four bytes of a re-encoded label without confirming that the xn-- prefix is present. Exploitation depends on stack layout and an application passing attacker-controlled labels to a ToUnicode API; outcomes include invalid-label acceptance or a process crash.
The record
- CVE
- CVE-2026-57053
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- The GnuPG Project
- Product
- Libidn
- Classifications
- CWE-1284, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.44
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- ToUnicode round-trip verification reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo