dbcve.org
Crypt\Application · Jonasbn

CVE-2026-58102

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-13
Fix available
A fix is available. Upgrade to 2.1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Crypt::OpenSSL::X509 Perl module before version 2.1.3 has a heap out-of-bounds read vulnerability when processing certificate extension OIDs. The OBJ_obj2txt() return value (full OID text length) is incorrectly used as the hash-key length instead of the actual bytes written to a fixed 129-byte buffer. When an OID exceeds 129 bytes, memory past the buffer allocation is read and exposed as the hash key.

MitigationUpgrade Crypt::OpenSSL::X509 to version 2.1.3 or later. Audit all Perl applications using this module to identify and remediate exposed systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Crypt\Application
Affected:< 2.1.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Crypt::OpenSSL::X509 is installed
    Run: perl -MCrypt::OpenSSL::X509 -e 'print $Crypt::OpenSSL::X509::VERSION'
    Affected if Module is not installed or command fails - not vulnerable in this case
  2. Identify installed version of Crypt::OpenSSL::X509
    Capture the version number from the previous command output
    Affected if Version number is below 2.1.3 (e.g., 2.1.2, 2.1.1, 2.0.x, 1.x)
  3. Check for Perl applications using this module
    Search for files containing 'use Crypt::OpenSSL::X509' or 'require Crypt::OpenSSL::X509' across your codebase: grep -r 'Crypt::OpenSSL::X509' /path/to/code --include='*.pl' --include='*.pm'
    Affected if Applications use this module AND the module version is below 2.1.3

You are affected if Crypt::OpenSSL::X509 version 2.1.2 or earlier is installed and actively used by any Perl application that processes X.509 certificates.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.3 or later
Fixed in 2.1.3
Interim mitigation

Upgrade Crypt::OpenSSL::X509 to version 2.1.3 or later. Audit all Perl applications using this module to identify and remediate exposed systems.

Recommended fix High confidence

2.1.3

  1. Check the current version of Crypt::OpenSSL::X509 installed by running: cpan -D Crypt::OpenSSL::X509 or perl -MCrypt::OpenSSL::X509 -e 'print $Crypt::OpenSSL::X509::VERSION'
  2. Upgrade to version 2.1.3 or later using cpan (cpan -i Crypt::OpenSSL::X509) or cpanm (cpanm Crypt::OpenSSL::X509)
  3. Verify the upgrade was successful by checking the installed version matches or exceeds 2.1.3
  4. Test that existing code relying on certificate extension parsing continues to function correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Crypt\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58102 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58102 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data