Is CVE-2026-54728 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-54728 being exploited in the wild.

How severe is CVE-2026-54728?

Informational severity, with a CVSS score of 6.1, published 16 July 2026.

Which products and versions are affected?

Bunkerity BunkerWeb < 1.6.12; Bunkerity BunkerWeb PRO < 0.57.

Is there a fix for CVE-2026-54728?

A patch was published on 2026-06-12: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-54728 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-54728?

Check whether you run Bunkerity BunkerWeb or Bunkerity BunkerWeb PRO at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-54728: Bunkerity BunkerWeb privilege escalation in UI and API

Q: Which products and versions are affected?

Bunkerity BunkerWeb < 1.6.12; Bunkerity BunkerWeb PRO < 0.57.

Q: Is there a fix for CVE-2026-54728?

A patch was published on 2026-06-12: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-54728 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-54728?

Check whether you run Bunkerity BunkerWeb or Bunkerity BunkerWeb PRO at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-54728 · Severity: info · CVSS 6.1 · Published 2026-07-16

BunkerWeb is a web application firewall (WAF) designed to protect websites from cyberattacks. A security flaw in its management interface and API could allow a user with low-level access to gain full administrative control. This risk only exists if the management interface is exposed directly to the network without being protected by the WAF itself. Exploiting this could allow an attacker to modify security settings, view sensitive logs, or disable the firewall entirely.

Technologies: Bunkerity BunkerWeb. Vendors: Bunkerity.

Quick answers

Is CVE-2026-54728 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-54728 being exploited in the wild.
How severe is CVE-2026-54728?: Informational severity, with a CVSS score of 6.1, published 16 July 2026.
Which products and versions are affected?: Bunkerity BunkerWeb < 1.6.12; Bunkerity BunkerWeb PRO < 0.57.
Is there a fix for CVE-2026-54728?: A patch was published on 2026-06-12: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54728 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-54728?: Check whether you run Bunkerity BunkerWeb or Bunkerity BunkerWeb PRO at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An authenticated privilege escalation vulnerability exists in the BunkerWeb UI and API due to improper validation of the Host header. When the UI or API is exposed directly (not behind a reverse proxy performing vhost validation), a low-privileged user can inject a crafted Host header to influence the generation of Biscuit authentication token facts. This allows the attacker to escalate their privileges to administrative levels. The root cause is a failure to properly neutralize user-controlled input in a configuration-dependent path used for token generation. The issue is fixed in BunkerWeb 1.6.12 and BunkerWeb PRO 0.57 by binding the Host header, client IP, and username as typed terms in the Biscuit tokens.

Affected products

Bunkerity BunkerWeb < 1.6.12
Bunkerity BunkerWeb PRO < 0.57

Timeline

2026-06-12: patched: Fix committed to repository
2026-07-02: advisory: Release v1.6.12 published
2026-07-08: advisory: GitHub Security Advisory published
2026-07-16: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.