# CVE-2026-58102 — JONASBN Crypt::OpenSSL::X509

> As of 2026-07-14, CVE-2026-58102 is a CRITICAL-severity vulnerability in JONASBN Crypt::OpenSSL::X509, CVSS v3.1 9.1, EPSS 0.1% (1.3th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-58102 as of 2026-07-14; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-07-14

## What is CVE-2026-58102?

Crypt::OpenSSL::X509 versions before 2.1.3 for Perl allow a heap out-of-bounds read via a long certificate extension OID in hv_exts. When building the extension hash (via extensions(), extensions_by_long_name(), extensions_by_oid(), or has_extension_oid()), the code passes OBJ_obj2txt()'s return value as the hash-key length; because that value is the OID's full text length rather than the bytes written to the fixed-size buffer (129 bytes), an OID whose text is longer than the 129-byte buffer causes a read past the allocation, exposing adjacent heap memory as the returned hash key. extensions_by_name() uses the static shortname path and is not affected.

The record classifies CVE-2026-58102 under weakness class [CWE-125](https://intel.threadlinqs.com/cwe/CWE-125). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 84 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 9.1 — CRITICAL (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **EPSS (FIRST):** 0.1% probability of exploitation in the next 30 days, higher than 1.3% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-13, last modified 2026-07-14

## Is CVE-2026-58102 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **JONASBN**: Crypt::OpenSSL::X509

## How to fix CVE-2026-58102

No vendor patch reference has been recorded for CVE-2026-58102 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-58102

No threat campaign in the Threadlinqs corpus currently references CVE-2026-58102, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on 2026-07-15. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com — patch](https://github.com/dsully/perl-crypt-openssl-x509/commit/757289bfce095455c104d4adfe9312e7b339620f.patch)
- [metacpan.org — release notes](https://metacpan.org/release/JONASBN/Crypt-OpenSSL-X509-2.1.3/source/Changes.md)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-58102
Full detection coverage and IOCs for threats exploiting CVE-2026-58102 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp