Skip to content
IoT

CVE-2026-62184

8.7
High
EPSS 0.78%Patch availableJul 14, 2026

Log parser lets attacker inject IP via username, causing banIP to block arbitrary hosts.

common questions

Is CVE-2026-62184 being exploited?

Not confirmed. CVE-2026-62184 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.78% probability of exploitation in the next 30 days.

How severe is CVE-2026-62184?

CVE-2026-62184 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-62184?

Yes. A fix has been recorded for CVE-2026-62184. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-62184 affect?

CVE-2026-62184 affects luci-app-banip (LuCI/OpenWrt), OpenWrt-based routers with banIP enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-62184?

Apply vendor patch when released; sanitize/validate inputs or disable banIP; restrict LuCI admin access.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
luci-app-banip (LuCI/OpenWrt)OpenWrt-based routers with banIP enabled
impact

Unauthenticated remote attacker can inject an IPv4 into logs via username, causing banIP to ban chosen IPs—enabling targeted DoS and evasion.

action required

Patch when possible

affected versions
openwrt luci-app-banip
  • affected<= 0.11.1
vendor says fixed ind9bbc372e29618a8807b693a1ccf6d0e42cd196c

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free