CVE-2026-62184: Improper Encoding or Escaping of Output in openwrt luci
A vulnerability in openwrt luci-app-banip allows an unauthenticated remote attacker to inject arbitrary IP addresses into log lines via attacker-controlled fields such as usernames. This causes the banIP feature to block incorrect IP addresses, leaving the real attacker unblocked. The issue arises from an awk-based log parser that extracts the first IPv4 address from log lines without validating its position. This affects luci versions up to and including 0.11.1 and has a high severity score of 8.7.
AI Analysis
Technical Summary
CVE-2026-62184 describes a log parsing vulnerability in openwrt's luci-app-banip component. The vulnerability is due to improper encoding or escaping of output, where the awk-based parser extracts the first IPv4 address from log lines regardless of its field position. An attacker can exploit this by injecting an IP address into the login username field, causing the banIP mechanism to block an incorrect IP address while the attacker remains unblocked. This can be exploited remotely without authentication. The affected versions are luci up to 0.11.1. No official patch or remediation level has been provided yet.
Potential Impact
An unauthenticated remote attacker can manipulate the banIP blocking mechanism by injecting arbitrary IP addresses into log entries. This results in the system blocking innocent IP addresses instead of the attacker's IP, effectively bypassing the intended IP blocking protection. This can lead to denial of service for legitimate users and failure to block malicious actors.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should be aware of this limitation in the banIP feature and consider alternative methods to block malicious IPs. No official fix or temporary workaround has been documented at this time.
CVE-2026-62184: Improper Encoding or Escaping of Output in openwrt luci
Description
A vulnerability in openwrt luci-app-banip allows an unauthenticated remote attacker to inject arbitrary IP addresses into log lines via attacker-controlled fields such as usernames. This causes the banIP feature to block incorrect IP addresses, leaving the real attacker unblocked. The issue arises from an awk-based log parser that extracts the first IPv4 address from log lines without validating its position. This affects luci versions up to and including 0.11.1 and has a high severity score of 8.7.
CVSS v4.0
Score 8.7high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-62184 describes a log parsing vulnerability in openwrt's luci-app-banip component. The vulnerability is due to improper encoding or escaping of output, where the awk-based parser extracts the first IPv4 address from log lines regardless of its field position. An attacker can exploit this by injecting an IP address into the login username field, causing the banIP mechanism to block an incorrect IP address while the attacker remains unblocked. This can be exploited remotely without authentication. The affected versions are luci up to 0.11.1. No official patch or remediation level has been provided yet.
Potential Impact
An unauthenticated remote attacker can manipulate the banIP blocking mechanism by injecting arbitrary IP addresses into log entries. This results in the system blocking innocent IP addresses instead of the attacker's IP, effectively bypassing the intended IP blocking protection. This can lead to denial of service for legitimate users and failure to block malicious actors.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, administrators should be aware of this limitation in the banIP feature and consider alternative methods to block malicious IPs. No official fix or temporary workaround has been documented at this time.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-13T16:36:32.094Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a555d1768715ace43ecab58
Added to database: 07/13/2026, 21:48:07 UTC
Last enriched: 07/13/2026, 22:03:02 UTC
Last updated: 07/14/2026, 01:51:57 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.