CVE-2025-22874 | Usage of ExtKeyUsageAny disables policy validation in crypto/x509

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.

Published: 2025-06-11 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-22874 is rated Low Risk (38.1/100): CVSS High severity, with low exploitation likelihood (EPSS 0.31%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-22874

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.08% 0.31% +0.23%
2 2026-04-07 0.02% 0.08% +0.06%
3 2025-06-12 — 0.02% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-22874

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-22874

OS Trackers for CVE-2025-22874

vendor priority summary link
alpine high CVE-2025-22874: 1 source package rows (go); 2 state rows across 2 repos (3.22-community, edge-community); fixed 2, open 0. https://security.alpinelinux.org/vuln/CVE-2025-22874
debian unimportant CVE-2025-22874 unimportant priority: Debian including 3 source packages (golang-1.15, golang-1.19, golang-1.24), 3 status rows across 3 suites (bookworm, bullseye, trixie): resolved 3. https://security-tracker.debian.org/tracker/CVE-2025-22874
redhat high — https://access.redhat.com/security/cve/CVE-2025-22874
suse high CVE-2025-22874 severity important: SUSE including 100 source package names (glib2-tools-2.76.2-6.1, go, …), 402 product×package rows across 34 product lines (Container bci/golang, Container suse/sl-micro/6.0/baremetal-os-container, … (34 product lines)): Fixed 254, Known Not Affected 148. https://www.suse.com/security/cve/CVE-2025-22874/
ubuntu medium CVE-2025-22874 medium priority: Ubuntu including 15 source packages (golang, golang-1.10, …), 108 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 57, needs-triage 45, ignored 3, not-affected 3. https://ubuntu.com/security/CVE-2025-22874

Affected software / configurations for CVE-2025-22874

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-22874

cvelogic Threat Intelligence