luci-app-banip contains a log parsing vulnerability where the awk-based parser extracts the first IPv4 address from log lines regardless of field position, allowing attackers to inject arbitrary IPs via attacker-controlled fields like usernames. An unauthenticated remote attacker can inject an IP address into the login username field, causing banIP to block the wrong target while the real attacker remains unblocked.
CVE-2026-62184
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 36.3%
- KEV
- Not listed
Published
July 13, 2026
Last Modified
July 15, 2026
Advisory Details (3)
Auto-updated Jul 13, 2026luci-app-banip Log Monitor IP Extraction Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/luci-app-banip-log-monitor-ip-extraction-bypasscommit d9bbc372e296 (openwrt/luci)
Fix landed in openwrt/luci commit d9bbc372e296 — awaiting tagged release
https://github.com/openwrt/luci/commit/d9bbc372e29618a8807b693a1ccf6d0e42cd196cluci-app-banip: log monitor extracts first IP from log lines — attacker-controlled fields cause wrong-target blocking · Advisory · openwrt/luci · GitHub
https://github.com/openwrt/luci/security/advisories/GHSA-r6hx-4f83-vp8mVendor Advisories for CVE-2026-62184(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 24× 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.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:21 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 06:16 UTCGHSA enrichment
- 2026-07-16 18:46 UTCGHSA enrichment
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 07:16 UTCGHSA enrichment
- 2026-07-15 19:45 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 08:14 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 20:44 UTCGHSA enrichment
- 2026-07-14 09:13 UTCGHSA enrichment
- 2026-07-13 21:43 UTCEG score recompute
- 2026-07-13 21:42 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-62184?
When was CVE-2026-62184 disclosed?
Is CVE-2026-62184 actively exploited?
What is the CVSS score of CVE-2026-62184?
How do I remediate CVE-2026-62184?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62184
Is Your Infrastructure Affected by CVE-2026-62184?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.