CVE-2026-39821
The ToASCII and ToUnicode functions incorrectly accept …
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".
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- go.dev/cl/767220
- go.dev/issue/78760
- groups.google.com/g/golang-announce/c/iI-mYSI0lu8
- pkg.go.dev/vuln/GO-2026-5026
- access.redhat.com/errata/RHSA-2026:23262
- access.redhat.com/errata/RHSA-2026:23264
- access.redhat.com/errata/RHSA-2026:26546
- access.redhat.com/errata/RHSA-2026:26547
- nvd.nist.gov/vuln/detail/CVE-2026-39821
- cve.org/CVERecord?id=CVE-2026-39821
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.