Skip to main content
VulnerabilityPublished

CVE-2026-75514: bunkerity bunkerweb · Reliance on Reverse DNS Resolution for a Security-Critical Action

Affects bunkerity bunkerwebSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 1.6.13 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.6.13
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade bunkerweb and bunkerity/bunkerweb to 1.6.13.

Affected software

ProductAffectedFixed in
bunkeritybunkerwebAffected
  • <1.6.13
Fixed in
  • 1.6.13
GitHubbunkerity/bunkerwebpkg:github/bunkerity/bunkerwebOther threatsAffected
  • <1.6.13
Fixed in
  • 1.6.13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade BunkerWeb to version 1.6.13 or later, where this issue is fixed by verifying that the hostname resolves back to the client IP address before trusting PTR suffix matches. No other mitigation or workaround is indicated.

Description

BunkerWeb is an open-source, next-generation Web Application Firewall. Prior to 1.6.13, the blacklist, greylist, and antibot modules in src/common/core/blacklist/blacklist.lua, src/common/core/greylist/greylist.lua, and src/common/core/antibot/antibot.lua trust PTR suffix matches in IGNORE_RDNS, GREYLIST_RDNS, and ANTIBOT_IGNORE_RDNS without using get_ips to confirm that the hostname resolves to the client address. An unauthenticated remote attacker who controls a PTR record can spoof a trusted suffix to bypass rDNS-based blacklisting, gain greylist treatment, or skip an antibot challenge. This issue is fixed in version 1.6.13.

References

Community reviews

Loading reviews…