dbcve.org
Crypt\Application · Jonasbn

CVE-2026-58101

HIGH · 7.5 CVSS v3.1 Published 2026-07-13
Fix available
A fix is available. Upgrade to 2.1.3 or later.
See remediation →
84/100
Remediation priority · High
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 denial of service via NULL pointer dereference. X509V3_EXT_d2i(ext) returns NULL when an extension's DER value fails to parse. basicC, ia5string, and auth_att dereference its result without a NULL check. keyid_data also dereferences akid->keyid, which is NULL for an empty AKI SEQUENCE (DER 30 00) even when the parse succeeds. A caller invoking an affected helper on an extension from an untrusted certificate triggers a SIGSEGV that crashes the Perl process.

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

Crypt::OpenSSL::X509 versions before 2.1.3 contain NULL pointer dereference vulnerabilities in three extension parsing helpers (basicC, ia5string, auth_att) and keyid_data. These functions fail to check if X509V3_EXT_d2i() returns NULL when DER parsing fails, or if akid->keyid is NULL for empty AKI SEQUENCE. An attacker can trigger a SIGSEGV by presenting a specially crafted certificate with malformed extensions.

MitigationUpgrade Crypt::OpenSSL::X509 to version 2.1.3 or later, which includes proper NULL pointer checks in the affected helper functions.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify installed version of Crypt::OpenSSL::X509
    Run 'perl -MCrypt::OpenSSL::X509 -e "print $Crypt::OpenSSL::X509::VERSION"' or check via 'cpan -m Crypt::OpenSSL::X509'
    Affected if Version is present but less than 2.1.3 (e.g., 2.1.2, 2.1.1, 2.0.0, 1.x.x)
  2. Verify the module is loadable
    Run 'perl -e "use Crypt::OpenSSL::X509"' to confirm the module is installed and accessible
    Affected if Module loads without error but version is below 2.1.3
  3. Check for code that parses X509 certificates
    Search codebase for calls to Crypt::OpenSSL::X509->new(), ->pem(), or ->der() that process external certificates
    Affected if Application loads and parses certificates using this module on affected version

You are affected if Crypt::OpenSSL::X509 is installed at a version below 2.1.3 and your code parses X509 certificates with this module.

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, which includes proper NULL pointer checks in the affected helper functions.

Recommended fix Moderate confidence

Crypt::OpenSSL::X509 version 2.1.3 or later

  1. Check the currently installed version of Crypt::OpenSSL::X509 by running: perl -MCrypt::OpenSSL::X509 -e 'print $Crypt::OpenSSL::X509::VERSION'
  2. Upgrade the module to version 2.1.3 or later using your Perl package manager. For cpanm: cpanm Crypt::OpenSSL::X509>=2.1.3, or for cpan: cpan install Crypt::OpenSSL::X509
  3. Verify the upgrade was successful by running: perl -MCrypt::OpenSSL::X509 -e 'print $Crypt::OpenSSL::X509::VERSION' and confirming the version is 2.1.3 or higher
  4. Test your application to ensure the upgrade does not break existing functionality

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

Fix this in Crypt\ Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58101 — 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-58101 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