dbcve.org
StorableApplication · Nwclark

CVE-2026-57433

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-13
Fix available
A fix is available. Upgrade to 3.41 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
Storable versions before 3.41 for Perl have a signed integer overflow when deserializing a crafted SX_HOOK record. retrieve_hook_common reads a signed 32-bit item count from an SX_HOOK record and calls av_extend with that count plus one. A count of I32_MAX wraps the addition to a negative value. A crafted blob passed to thaw or retrieve triggers the overflow; av_extend receives the negative count and dies with a panic, terminating the deserialization.

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 Perl Storable module versions before 3.41 contain a signed integer overflow in the retrieve_hook_common function when deserializing SX_HOOK records. The function reads a signed 32-bit item count from a crafted record and adds one before passing to av_extend. When the count equals I32_MAX (2147483647), the addition wraps to a negative value, causing av_extend to panic and terminate deserialization.

MitigationUpgrade Storable to version 3.41 or later. As a defense-in-depth measure, avoid deserializing untrusted Storable blobs using thaw or retrieve 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
StorableApplication
Affected:< 3.41

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Check installed Storable module version
    Run: perl -MStorable -e 'print $Storable::VERSION . "\n"'
    Affected if Version is present and less than 3.41 (for example, 3.40, 3.30, etc.)
  2. Verify if Storable thaw or retrieve functions are used
    Search Perl codebases for calls to Storable::thaw, Storable::retrieve, or the functional equivalents (thaw, nfreeze, retrieve, fdretrieve)
    Affected if Code deserializes Storable blobs from untrusted sources using thaw or retrieve functions; this is required to trigger the vulnerable code path
  3. Confirm SX_HOOK record deserialization is possible
    If using Storable::retrieve or Storable::thaw on data from external/untrusted sources, the vulnerable code path in retrieve_hook_common can be invoked
    Affected if Data containing SX_HOOK records from untrusted sources is deserialized; the vulnerability triggers when a crafted record contains I32_MAX (2147483647) as the item count

You are affected if Storable version is below 3.41 AND your code deserializes untrusted Storable data using thaw or retrieve functions, which enables the crafted SX_HOOK record to trigger the integer overflow.

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 3.41 or later
Fixed in 3.41
Interim mitigation

Upgrade Storable to version 3.41 or later. As a defense-in-depth measure, avoid deserializing untrusted Storable blobs using thaw or retrieve functions.

Recommended fix High confidence

Storable 3.41

  1. Upgrade the Perl Storable module to version 3.41 or later using your preferred method: 'cpan -i Storable' or 'cpanm Storable'
  2. Alternatively, update via your system package manager if Storable was installed via system packages
  3. Verify the upgrade was successful by running 'perl -MStorable -e "print $Storable::VERSION"' and confirming it shows 3.41 or higher
  4. If using Storable in production systems, test that existing serialized data can still be deserialized with the new version
Caveat Minor patch releases typically have no breaking changes, but test deserialization of existing stored data after upgrading

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

Fix this in Storable Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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