CVE-2025-61727: Golang 1.24 · An excluded subdomain constraint in a certificate chain does not restrict the usage of
Affects golang-1.24Source GCVE Database
Not known to be exploited · CVSS 6.5 Medium.
Data as of 17 Nov 2026, 20:52 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSgolang-1.24pkg:deb/ubuntu/golang-1.24?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSgolang-1.25pkg:deb/ubuntu/golang-1.25?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 25.10golang-1.24pkg:deb/ubuntu/golang-1.24?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10golang-1.25pkg:deb/ubuntu/golang-1.25?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSgolang-1.24pkg:deb/ubuntu/golang-1.24?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSgolang-1.24pkg:deb/ubuntu/golang-1.24?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
A vulnerability in Golang 1.24 allows an excluded subdomain constraint in a certificate chain to be bypassed by wildcard Subject Alternative Names (SANs) in the leaf certificate. This means that a constraint excluding a specific subdomain, such as test.example.com, does not prevent a leaf certificate from using a wildcard SAN like *.example.com, potentially allowing unauthorized usage of the excluded subdomain.