CVE Tools

CVE-2025-22865

ParsePKCS1PrivateKey panic with partial keys in crypto/x509

CVE-2025-22865 affects Go standard library crypto/x509 (CVSS 7.5, High).

No known exploitation. EPSS puts it in the 49th percentile. Fixed in 1.24.0-rc.2.

Check it yourself

OpenVAS · 10 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.857009

Run the check

Published Updated Sources: CVE.org, NVD, BDU

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.0-rc.2Upgrade to: 1.24.0-rc.2Stated by: CVE record
  • Red Hat Inc. Red Hat StorageAffected: 3Upgrade to: not statedStated by: BDU
  • Red Hat Inc. Red Hat 3scale API Management PlatformAffected: 2Upgrade to: not statedStated by: BDU
  • Red Hat Inc. Red Hat Ceph StorageAffected: 5Upgrade to: not statedStated by: BDU
  • The Go Project GoAffected: before 1.24Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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

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.

EPSS49th
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.6% chance of exploitation activity in the next 30 days, which ranks it in the 49th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

4 events over 513 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablepublished, record updated

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Sources

Questions about CVE-2025-22865

Is CVE-2025-22865 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.6%.
Which versions are affected by CVE-2025-22865?
Crypto/x509: ≥ 1.24.0-0, < 1.24.0-rc.2. Red Hat Storage: 3. Red Hat 3scale API Management Platform: 2. 2 more products are listed in the record.
How do I fix or mitigate CVE-2025-22865?
Upgrade to 1.24.0-rc.2 or later. The advisory is on access.redhat.com.

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.