Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V6 - Authentication IP-independent access control
|
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 14, 2026
Log integrity spoofing in Eclipse Kura before 5.6.2 lets an unauthenticated remote attacker forge the client IP recorded in audit logs by supplying a crafted X-Forwarded-For header, because the Jetty ForwardedRequestCustomizer is installed unconditionally on every connector and getRemoteAddr() reflects the header value. This enables bypass of IP-based brute-force defenses like fail2ban (spoofing a non-routable source to evade bans) or a denial of service against a third party by injecting a victim IP so their address is banned. No public exploit is identified at time of analysis and it is not on CISA KEV; CVSS 4.0 base score is 8.8.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Know when Eclipse Kura gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
Primary rating from Vendor (eclipse) · only source for this CVE.
CVSS VectorVendor: eclipse
DescriptionCVE.org
Eclipse Kura versions prior to 5.6.2 trust the client-supplied X-Forwarded-For HTTP header as the authoritative source of the client IP address in audit log entries. The org.eclipse.kura.web2 (Web Console) and org.eclipse.kura.rest.provider (REST API) components use this header as the primary IP source when initializing audit context, and org.eclipse.kura.jetty.customizer unconditionally installs Jetty's ForwardedRequestCustomizer on all HTTP/HTTPS connectors, causing HttpServletRequest.getRemoteAddr() to reflect the attacker-controlled header value. An unauthenticated remote attacker can exploit this vulnerability to bypass IP-based brute-force protections - such as fail2ban - by spoofing the logged IP address to a non-routable value, allowing a brute-force attack to proceed undetected, or to cause a denial of service against a third party by injecting a victim's IP address and triggering a ban on that address.
Executive ViewAI
Eclipse Kura vulnerability CVE-2026-9561 (CVSS 8.8) allows unauthenticated attackers to hide their identity in audit logs and impersonate legitimate user IP addresses, creating forensic blind spots and enabling account lockouts against innocent parties. Organizations face compromised audit integrity, failed investigations, and operational disruption in IoT and edge device management environments until the vulnerability is patched.
Within 24 hours: identify all Eclipse Kura deployments and verify which run versions prior to 5.6.2; assess whether instances are exposed to untrusted networks or rely on IP-based brute-force defenses. Within 7 days: disable X-Forwarded-For header processing if no legitimate reverse-proxy environment exists; implement layered brute-force defenses beyond IP blocking (e.g., account lockout, CAPTCHA); enable raw request header logging to detect spoofing attempts. Within 30 days: monitor Eclipse Kura release channels for 5.6.2 availability and execute upgrades on all affected systems; review and remediate X-Forwarded-For trust assumptions across reverse-proxies and load balancers.
No vendor-released patch identified at time of analysis. Interim mitigations: disable X-Forwarded-For header processing if legitimate reverse-proxy use does not require it; implement network-level header filtering at ingress to strip or validate X-Forwarded-For; transition IP-based brute-force defenses to multi-factor approaches (account lockout, rate limiting, behavioral analysis); deploy comprehensive request header logging to detect spoofing; isolate critical Kura instances from untrusted networks if operationally feasible.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
EUVD-2026-43636
GHSA-fqc6-vqq8-5xwp
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB