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.
CVE-2026-9561
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 90% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- 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
- 8.8
- EG Score
- 8.8(medium)
- EPSS
- 10.5%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
July 14, 2026
Advisory Details (1)
Auto-updated Jul 14, 2026Eclipse Kura IP Spoofing via X-Forwarded-For Header (#117) · Issues · Eclipse Projects Security / cve-assignment · GitLab
https://gitlab.eclipse.org/security/cve-assignment/-/work_items/117Vendor Advisories for CVE-2026-9561(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× 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-15 21:32 UTCEG score recompute
- 2026-07-15 21:32 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 09:10 UTCEG score recompute
- 2026-07-15 09:10 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 20:47 UTCEG score recompute
- 2026-07-14 20:47 UTCGHSA enrichment
- 2026-07-14 08:25 UTCEG score recompute
- 2026-07-14 08:25 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-9561?
When was CVE-2026-9561 disclosed?
Is CVE-2026-9561 actively exploited?
What is the CVSS score of CVE-2026-9561?
How do I remediate CVE-2026-9561?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-9561
Is Your Infrastructure Affected by CVE-2026-9561?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.