# CVE-2026-61718: bunkerweb: Read-only Web UI users can delete job cache files due to missing authorization on /cache/ routes

> Read-only users can delete critical WAF cache files due to missing authorization checks on cache routes, impacting data integrity.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **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:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-q7rm-935c-v39g

## What is CVE-2026-61718?

CVE-2026-61718 is a medium-severity missing authorization vulnerability in bunkerity bunkerweb, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

bunkerweb is an Open-source and next-generation Web Application Firewall (WAF). From 1.6.2 until 1.6.12, the BunkerWeb web UI BiscuitMiddleware authorization bypass list included the /cache/ URL prefix, so routes in src/ui/app/routes/cache.py protected only by @login_required, including POST /cache/delete, allowed low-privilege read-only reader accounts to permanently delete job cache files containing blacklist, greylist, DNSBL, CrowdSec, GeoIP, ModSecurity CRS, Let's Encrypt, ACME, and custom configuration data. This issue is fixed in version 1.6.12.

Weakness: CWE-862 (Missing Authorization), CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2026-61718 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61718 is a medium-severity missing authorization vulnerability in bunkerity bunkerweb, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61718 in the wild and no public exploit code.

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

## Sources

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

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