CVE-2025-61727
Improper application of excluded DNS name constraints when verifying wildcard names in crypto/x509
CVE-2025-61727 is a weak cert validation in The Go Project Go (CVSS 6.5, Medium).
No known exploitation. EPSS puts it in the 24th percentile. Fixed versions are out.
No public exploit knownFix5 products2 fixed builds listed below
e.g. OID 1.3.6.1.4.1.25623.1.0.136508
What to do
Find your product and version, then upgrade to the build on the right.
- Go standard library crypto/x509Affected: < 1.24.11Upgrade to: 1.24.11Affected: ≥ 1.25.0, < 1.25.5Upgrade to: 1.25.5Stated by: CVE record
- Golang GoAffected: < 1.24.11Upgrade to: 1.24.11Stated by: NVD
- RED SOFT RED OSAffected: 7.3Upgrade to: not statedStated by: BDU
- The Go Project GoAffected: before 1.24.11Upgrade to: not statedStated by: BDU
- SberTech Platform V SberLinux OS ServerAffected: 9.2.0-fstecUpgrade to: not statedStated by: BDU
Versions as the sources state them. 1 more product has version data. Full version matrix after sign-in
What it is
From the CVE record
An excluded subdomain constraint in a certificate chain does not restrict the usage of wildcard SANs in the leaf certificate. For example a constraint that excludes the subdomain test.example.com does not prevent a leaf certificate from claiming the SAN *.example.com.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.3% chance of exploitation activity in the next 30 days, which ranks it in the 24th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
8 events over 319 days, from the signal feeds we watch.
- Patch availablerecord updated
- OpenVAS check added
- Patch availablerecord updated
- Publishedweakness classified, att&ck mapped
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Scored 6.5 by NVD.
How it is reached
- Attack Vector NetworkExploitable remotely over the network without any special conditions
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality LowSome restricted information is disclosed, but limited in scope
- Integrity LowData modification is possible but limited in scope or consequence
- Availability NoneNo availability impact
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
Sources
References in the record
And 5 more references. See all after sign-in
Questions about CVE-2025-61727
- Is CVE-2025-61727 being exploited?
- No exploitation is confirmed and no public exploit is known. EPSS puts the chance of exploitation in the next 30 days at 0.3%.
- Which versions are affected by CVE-2025-61727?
- Go: before 1.24.11. Crypto/x509: < 1.24.11; ≥ 1.25.0, < 1.25.5. Go: < 1.24.11. 3 more products are listed in the record.
- How do I fix or mitigate CVE-2025-61727?
- Upgrade to a fixed build for your product branch: 1.24.11, 1.25.5.
Last updated
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Go, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI