CVE-2026-58102
Heap out-of-bounds read in Crypt::OpenSSL::X509 when parsing long certificate extension OIDs.
Is CVE-2026-58102 being exploited?
Not confirmed. CVE-2026-58102 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-58102?
CVE-2026-58102 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-58102?
Yes. A fix has been recorded for CVE-2026-58102. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-58102 affect?
CVE-2026-58102 affects Crypt::OpenSSL::X509 < 2.1.3, Perl applications that parse certificates (mail servers, TLS clients, CA tools), CPAN modules embedding this library. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-58102?
Upgrade Crypt::OpenSSL::X509 to >= 2.1.3 and restart dependent services.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Heap OOB read via crafted certificate extension OID allowing disclosure of adjacent heap memory (possible leakage of private keys, credentials).
Immediate action required
- affected< 2.1.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.