CVE-2025-22874
Usage of ExtKeyUsageAny disables policy validation in crypto/x509
CVE-2025-22874 affects Go standard library crypto/x509 (CVSS 7.5, High).
No known exploitation. EPSS puts it in the 32nd percentile. Fixed in 1.24.4.
No public exploit knownFix1.24.4Upgrade to this build
e.g. OID 1.3.6.1.4.1.25623.1.0.118831
What to do
Find your product and version, then upgrade to the build on the right.
- Go standard library crypto/x509Affected: ≥ 1.24.0-0, < 1.24.4Upgrade to: 1.24.4Stated by: CVE record
- RED SOFT RED OSAffected: 7.3Upgrade to: not statedStated by: BDU
- The Go Project GoAffected: from 1.24.0-0 before 1.24.4Upgrade to: not statedStated by: BDU
- KNS GRUPP Tatlin-ObdzhektAffected: before 1.10Upgrade to: not statedStated by: BDU
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.
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.4% chance of exploitation activity in the next 30 days, which ranks it in the 32nd percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
4 events over 379 days, from the signal feeds we watch.
- OpenVAS check added
- Patch availablerecord updated
- Published
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:N/I:H/A:N
Scored 7.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 NoneNo confidentiality impact
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability NoneNo availability impact
Sources
References in the record
And 6 more references. See all after sign-in
Questions about CVE-2025-22874
- Is CVE-2025-22874 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.4%.
- Which versions are affected by CVE-2025-22874?
- Crypto/x509: ≥ 1.24.0-0, < 1.24.4. RED OS: 7.3. Go: from 1.24.0-0 before 1.24.4. 1 more product is listed in the record.
- How do I fix or mitigate CVE-2025-22874?
- Upgrade to 1.24.4 or later.
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 Crypto/x509, 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