dbcve.org
Sereal\Application · Yves

CVE-2024-14030

HIGH · 8.1 CVSS v3.1 Published 2026-03-31
Fix available
A fix is available. Upgrade to 4.010 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Sereal::Decoder versions from 4.000 through 4.009_002 for Perl embeds a vulnerable version of the Zstandard library. Sereal::Decoder embeds a version of the Zstandard (zstd) library that is vulnerable to CVE-2019-11922. This is a race condition in the one-pass compression functions of Zstandard prior to version 1.3.8 could allow an attacker to write bytes out of bounds if an output buffer smaller than the recommended size was used.

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

Sereal::Decoder for Perl versions 4.000 through 4.009_002 embeds a vulnerable version of the Zstandard (zstd) compression library prior to 1.3.8. This embedded library contains CVE-2019-11922, a race condition in one-pass compression functions that can allow out-of-bounds writes when an output buffer smaller than recommended size is used.

MitigationUpgrade Sereal::Decoder to a version that embeds Zstandard 1.3.8 or later, or ensure any code using the decoder supplies output buffers sized according to Zstandard's recommended guidelines.

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
Sereal\Application
Affected:>= 4.000, < 4.010

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 if Sereal::Decoder Perl module is installed
    Run 'perl -MSereal::Decoder -e 'print $Sereal::Decoder::VERSION'" or use 'cpan -D Sereal::Decoder'
    Affected if Module is not installed or command fails - not affected. If installed, continue to version check.
  2. Verify the installed Sereal::Decoder version
    Compare the version number from step 1 against the affected range: >= 4.000 and < 4.010
    Affected if Version falls within >= 4.000 and < 4.010 - potentially affected by the embedded vulnerable zstd library.
  3. Confirm the Sereal::Decoder is actively used in your application
    Search Perl source code or running processes for 'use Sereal::Decoder' or 'Sereal::Decoder->new()' calls
    Affected if The module is installed but not loaded or used - likely not exploitable in your environment.
  4. Determine if decoded data originates from untrusted sources
    Audit code paths where Sereal::Decoder is used - check if input data comes from network, user upload, or other untrusted sources
    Affected if Decoder processes only trusted/internal data - exploitation risk is significantly reduced.

You are affected if Sereal::Decoder version is >= 4.000 and < 4.010 AND your application uses it to decode untrusted Sereal data.

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

Upgrade Sereal::Decoder to a version that embeds Zstandard 1.3.8 or later, or ensure any code using the decoder supplies output buffers sized according to Zstandard's recommended guidelines.

Recommended fix High confidence

4.010

  1. Check current Sereal::Decoder version by running 'perl -MSereal::Decoder -e 'print $Sereal::Decoder::VERSION'
  2. Upgrade Sereal::Decoder to version 4.010 or later using your Perl module installer, for example: 'cpanm Sereal::Decoder' or 'cpan Sereal::Decoder'
  3. Verify the upgrade was successful by checking the version again
Caveat Sereal protocol upgrades are typically backward compatible; however, test your application after upgrading

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

Fix this in Sereal\ Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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