Using ParsePKCS1PrivateKey to parse a RSA key that is missing the CRT values would panic when verifying that the key is well formed.
Loading...
Loading...
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-01-28. NVD baseline CVSS 7.5; sources differ by 0.0.
Using ParsePKCS1PrivateKey to parse a RSA key that is missing the CRT values would panic when verifying that the key is well formed.
January 28, 2025
April 15, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rhceph/snmp-notifier-rhel9:1.2.1-124 | 2025-07-28 | redhat |
| redhat | rhceph/grafana-rhel9:11.6.2-4 | 2025-07-24 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| stdlib | — | 1.24.0-rc.2 | — |
Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-22865
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.