CVE-2026-61718

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
5.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
22.8%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 17, 2026

Advisory Details (3)

Auto-updated Jul 17, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Read-only Web UI users can delete job cache files due to missing authorization on /cache/ routes · Advisory · bunkerity/bunkerweb · GitHub

https://github.com/bunkerity/bunkerweb/security/advisories/GHSA-q7rm-935c-v39g
github_release Patch Available

v1.6.12

Patch available: bunkerity/bunkerweb v1.6.12

https://github.com/bunkerity/bunkerweb/releases/tag/v1.6.12
github_commit

commit 685ccbbe7d20 (bunkerity/bunkerweb)

Fix landed in bunkerity/bunkerweb commit 685ccbbe7d20 — awaiting tagged release

https://github.com/bunkerity/bunkerweb/commit/685ccbbe7d204132a843a7b7fd802d1bdb3f20a9

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:21 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:25 UTCEPSS rescore
  7. 2026-07-21 15:25 UTCEPSS rescore
  8. 2026-07-20 17:08 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 02:34 UTCEG score recompute
  11. 2026-07-19 02:29 UTCEPSS rescore
  12. 2026-07-18 10:04 UTCEPSS rescore
  13. 2026-07-16 19:45 UTCEG score recompute
  14. 2026-07-16 19:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-61718?
CVE-2026-61718 is a medium vulnerability published on July 16, 2026. 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…
When was CVE-2026-61718 disclosed?
CVE-2026-61718 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61718 actively exploited?
CVE-2026-61718 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-61718?
CVE-2026-61718 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-61718?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61718, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-61718

Explore →

Is Your Infrastructure Affected by CVE-2026-61718?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.