Skip to main content
VulnerabilityPublished Updated

CVE-2026-48959: PMQS IO::Uncompress::Unzip · Inefficient Algorithmic Complexity

Affects PMQS IO::Uncompress::UnzipSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2.220 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.220
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade IO::Uncompress::Unzip and IO-Compress to 2.220.

Affected software

ProductAffectedFixed in
PMQSIO::Uncompress::UnzipAffected
  • <2.220
Fixed in
  • 2.220
GitHubIO-Compresspkg:github/IO-CompressOther threatsAffected
  • <2.220
Fixed in
  • 2.220

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until then, avoid processing untrusted zip files with vulnerable versions of IO::Uncompress::Unzip or implement external controls to limit resource consumption during decompression.

Description

IO::Uncompress::Unzip versions before 2.220 for Perl allow CPU exhaustion via per-byte read loop in fastForward.fastForward() compares length $offset (the digit count of the offset, 1 to 19) against the chunk size $c instead of $offset itself, so $c shrinks from 16 KiB to 1-19 bytes per iteration. Extracting a named entry from an attacker supplied zip via IO::Uncompress::Unzip->new($zip, Name => $target) drives a per-byte read loop scaling with the entry's compressed size, up to the non-Zip64 4 GiB cap.

References

Community reviews

Loading reviews…