CVE-2026-39821: Invoking failure to reject ASCII-only Punycode-encoded labels in golang.org/x/net/idna
Invoking failure to reject ASCII-only Punycode-encoded labels in golang.org/x/net/idna
Other sources
The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label. For example, ToUnicode("xn--example-.com") incorrectly returns the name "example.com" rather than an error. This behavior can lead to privilege escalation in programs using the idna package. For example, a program which performs privilege checks on the ASCII hostname may reject "example.com" but permit "xn--example-.com". If that program subsequently converts the ASCII hostname to Unicode, it will inadvertently permits access to the Unicode name "example.com".
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/golang-golang-x-netto a version that resolves this vulnerability.Fixed in 1:0.55.0-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.7.0-6 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 19.0.4-10 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.25.11-2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 25.0.3-18 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.30.10-25 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.6.1-3 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.7.7-13 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.15.0.aks0-11 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.26.4-2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.12.0-6 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.7.0-4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.19.1.kata3-3 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.9.5-14 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.15.0-5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.5.30-2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.62.0-5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.12.15-8 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.32.0-6 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.3.0-2 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.7.5-17 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.7.1-5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.0.10-6 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.14.1-13 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.14.4-11 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.7.7-4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.63.0-4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.0.2-8 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.31.0-21 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.8.2-4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.10.182-4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.24.2-28 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.22.0-3 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.1.6-3 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.62.0-16 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 25.0.7-3 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.11.4-17 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.5.1-4 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.27.0-11 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.25.1-5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 8.7.11-6 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.14.0-13
Event History
Frequently Asked Questions
What is the severity of CVE-2026-39821?
CVE-2026-39821 has a risk rating of 51, indicating a moderate severity level.
How do I fix CVE-2026-39821?
To fix CVE-2026-39821, update to the latest version of golang.org/x/net/idna that addresses this vulnerability.
What impact does CVE-2026-39821 have on my applications?
CVE-2026-39821 may lead to privilege escalation due to improper validation of Punycode-encoded labels in applications utilizing the affected IDNA functions.
What specific functions are affected by CVE-2026-39821?
The ToASCII and ToUnicode functions in golang.org/x/net/idna are affected by CVE-2026-39821.
Are there any known exploits for CVE-2026-39821?
As of now, there are no public exploits reported for CVE-2026-39821, but its presence may offer risk in vulnerable applications.