CVE-2025-22865 | ParsePKCS1PrivateKey panic with partial keys in crypto/x509

Using ParsePKCS1PrivateKey to parse a RSA key that is missing the CRT values would panic when verifying that the key is well formed.

Published: 2025-01-28 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-22865 is rated Moderate Risk (45.2/100): CVSS High severity, with low exploitation likelihood (EPSS 0.56%). Review affected assets and schedule remediation.

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-22865

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.13% 0.56% +0.43%
2 2026-03-03 0.17% 0.13% -0.04%
3 2026-02-24 — 0.17% —

Full EPSS history (9 records total)

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

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:H/I:N/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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-22865

OS Trackers for CVE-2025-22865

vendor priority summary link
debian unimportant CVE-2025-22865 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-22865
redhat high — https://access.redhat.com/security/cve/CVE-2025-22865
suse high CVE-2025-22865 severity important: SUSE including 36 source package names (go, go-doc, …), 285 product×package rows across 46 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (46 product lines)): Known Not Affected 176, Fixed 109. https://www.suse.com/security/cve/CVE-2025-22865/
ubuntu medium CVE-2025-22865 medium priority: Ubuntu including 15 source packages (golang, golang-1.10, …), 116 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 65, needs-triage 38, ignored 10, not-affected 3. https://ubuntu.com/security/CVE-2025-22865

Affected software / configurations for CVE-2025-22865

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-22865

cvelogic Threat Intelligence