CVE-2026-3381
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 · uneditedCompress::Raw::Zlib versions through 2.219 for Perl use potentially insecure versions of zlib. Compress::Raw::Zlib includes a copy of the zlib library. Compress::Raw::Zlib version 2.220 includes zlib 1.3.2, which addresses findings fron the 7ASecurity audit of zlib. The includes fixs for CVE-2026-27171.
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 confidenceCompress::Raw::Zlib, a Perl module for compression, bundles a copy of the zlib library. Versions through 2.219 include an insecure version of zlib that contains vulnerabilities (including CVE-2026-27171). Version 2.220 upgrades the bundled zlib to 1.3.2, which addresses findings from a 7ASecurity security audit.
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<= 2.219CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Compress::Raw::Zlib is installedRun `perl -MCompress::Raw::Zlib -e 'print $Compress::Raw::Zlib::VERSION'` to retrieve the installed versionAffected if The module is not installed or returns no version
-
Verify the installed version against affected rangeCompare the reported version number to the affected range: versions 2.219 and earlier are vulnerableAffected if The installed version is 2.219 or lower (for example, 2.218, 2.200, 1.0, etc.)
-
Confirm the module bundles zlibInspect the Compress::Raw::Zlib installation directory for a bundled zlib library file (typically zlib.pm or related zlib files in the module distribution)Affected if The module distribution contains bundled zlib code and the version is 2.219 or earlier
A user is affected if Compress::Raw::Zlib version 2.219 or earlier is installed, since these versions bundle the vulnerable zlib library.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Compress::Raw::Zlib to version 2.220 or later to obtain the patched zlib 1.3.2 library. This is a critical severity issue (CVSS 9.8) due to the bundled vulnerable zlib code.
Compress::Raw::Zlib version 2.220
- Update Compress::Raw::Zlib to version 2.220 or later using your Perl module management tool (e.g., 'cpan Compress::Raw::Zlib' or 'cpanm Compress::Raw::Zlib' or your system's package manager)
- Verify the installed version is 2.220 or later by running 'perl -MCompress::Raw::Zlib -e 'print $Compress::Raw::Zlib::VERSION'
- If using a packaged Perl installation (e.g., from Linux distribution), update the perl or libcompress-raw-zlib-perl package via your system package manager
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3381 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3381 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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