# CVE-2026-61455: Grav before 2.0.1 Decompression Bomb via ZipArchiver

> Attackers can cause denial of service by uploading crafted ZIP archives that exhaust disk space in Grav CMS.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-jxpj-m582-7727

## What is CVE-2026-61455?

CVE-2026-61455 is a high-severity denial of service vulnerability in getgrav grav, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Grav before 2.0.1 contains a decompression bomb vulnerability in ZipArchiver::extract() that lacks limits on uncompressed size, file count, and nesting depth. Attackers can supply a crafted ZIP archive that expands to fill available disk space, causing denial of service by exhausting storage resources.

Weakness: CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

## Which versions are affected by CVE-2026-61455?


## How do I fix CVE-2026-61455?

No fix has been published for CVE-2026-61455 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-61455 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61455 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61455 and fix it if it is affected.

What it is: CVE-2026-61455 is a high-severity denial of service vulnerability in getgrav grav, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61455 exists.

Affected product: getgrav grav. 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-2026-61455/ (Markdown: https://insights.sbomify.com/CVE-2026-61455/index.md)
```

## Sources

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

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