CVE-2026-58102: Jonasbn Crypt::openssl::x509 out-of-bounds read (CVSS 9.1)

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityNone

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Affected products

Jonasbn Crypt::openssl::x509< 2.1.3

Remediation

Fixed in

Jonasbn Crypt::openssl::x509≥ 2.1.3

Patch & vendor advisories

https://github.com/dsully/perl-crypt-openssl-x509/commit/757289bfce095455c104d4adfe9312e7b339620f.patch

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-58102 being actively exploited?

CVE-2026-58102 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.34%.

How severe is CVE-2026-58102?

CVE-2026-58102 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.34% probability of exploitation.

Which products are affected by CVE-2026-58102?

Affected products include Jonasbn Crypt::openssl::x509.

How do I fix CVE-2026-58102?

Upgrade affected software to a fixed version, for example Jonasbn Crypt::openssl::x509 2.1.3 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-58102 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo