# CVE-2025-15649: Denial of service in IO::Uncompress::Unzip

> An attacker can cause a denial of service by providing a zip file with a malformed DOS date, triggering an uncaught exception in the Perl library.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 29 May 2026
- **Also known as:** AZL-89283, BELL-CVE-2025-15649, DEBIAN-CVE-2025-15649, ECHO-6de8-d6d9-d48a, GHSA-hcq9-8v5x-mqjp, ROOT-OS-DEBIAN-11-CVE-2025-15649, UBUNTU-CVE-2025-15649

## What is CVE-2025-15649?

CVE-2025-15649 is a medium-severity denial of service vulnerability in PMQS IO::Uncompress::Unzip, published on 27 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IO::Uncompress::Unzip versions before 2.215 for Perl propagate uncaught exception when parsing zip header with malformed DOS date.

_dosToUnixTime() decodes the local-file-header last-modification date field and calls Time::Local::timelocal() without an eval guard. A header whose date field decodes to an out-of-range month, day, or hour causes timelocal() to die.

The exception propagates out of IO::Uncompress::Unzip->new($file) where callers expect undef plus $UnzipError.

Weakness: CWE-248 (Uncaught Exception)

## Which versions are affected by CVE-2025-15649?


## How do I fix CVE-2025-15649?

Upgrade to a fixed version.

## Is CVE-2025-15649 being exploited?

There is no known exploitation of CVE-2025-15649 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15649 and fix it if it is affected.

What it is: CVE-2025-15649 is a medium-severity denial of service vulnerability in PMQS IO::Uncompress::Unzip, published on 27 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-15649 in the wild and no public exploit code.

Affected product: PMQS IO::Uncompress::Unzip. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15649/ (Markdown: https://insights.sbomify.com/CVE-2025-15649/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15649
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15649
- OSV: https://osv.dev/vulnerability/CVE-2025-15649

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15649/
Summaries are generated and may contain mistakes; the official description above is the record.