Go standard library · Go · published 2026-05-22
CVE-2026-39821Invoking failure to reject ASCII-only Punycode-encoded labels in golang.org/x/net/idna
This month EPSS 1.8% with high severity (CVSS 9.6).
CVE-2026-39821 is not known to be exploited in the wild. EPSS estimates a 1.8% chance of exploitation in the next 30 days, higher than 79% of all CVEs. This Go vulnerability: CVSS 9.6 (v3.1), a successful attack gives total control of the component. Fixed upstream in Go 1.26.6, 1.25.13. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Go 1.26.6, 1.25.13.
Patch events
Language runtimeGo
Go security releases: 1.26.6, 1.25.13
Upgrade to
1.26.61.25.13Why: CVE-2026-39821: EPSS 1.8% with high severity (CVSS 9.6).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 1.8% (79th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.6 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Go standard library net/http
0to before1.25.13(affected)1.26.0-0to before1.26.6(affected)1.27.0-0to before1.27.0-rc.3(affected)
- Go standard library net/http/internal/http2
0to before1.25.13(affected)1.26.0-0to before1.26.6(affected)1.27.0-0to before1.27.0-rc.3(affected)
- golang.org/x/net golang.org/x/net/idna
0to before0.55.0(affected)
Description (from the CVE record)#
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".
Quoted from the CVE Program record.