# CVE-2026-9561: Security feature bypass in Eclipse Kura

> Attackers can spoof IP addresses in audit logs to bypass brute-force protections or trigger denial-of-service against third parties.

- **Severity:** High 8.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-fqc6-vqq8-5xwp

## What is CVE-2026-9561?

CVE-2026-9561 is a high-severity vulnerability in Eclipse Kura, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision), CWE-348 (Use of Less Trusted Source), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-9561?

It affects 1 product.


Products: Eclipse Kura.

## How do I fix CVE-2026-9561?

No fix has been published for CVE-2026-9561 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9561 being exploited?

There is no known exploitation of CVE-2026-9561 in the wild and no public exploit code.

## Other vulnerabilities in Eclipse Kura

- [CVE-2017-7649](https://insights.sbomify.com/CVE-2017-7649/): Auth bypass in Eclipse Kura Installer (critical 9.8)
- [CVE-2024-3046](https://insights.sbomify.com/CVE-2024-3046/): Eclipse Kura LogServlet vulnerability (high 7.5)
- [CVE-2019-10244](https://insights.sbomify.com/CVE-2019-10244/): XML external entity in Eclipse Kura (high 7.5)
- [CVE-2019-10242](https://insights.sbomify.com/CVE-2019-10242/): Path traversal in Eclipse Kura (medium 5.3)
- [CVE-2019-10243](https://insights.sbomify.com/CVE-2019-10243/): Information disclosure in Eclipse Kura (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9561 and fix it if it is affected.

What it is: CVE-2026-9561 is a high-severity vulnerability in Eclipse Kura, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9561 in the wild and no public exploit code.

Affected product: Eclipse Kura. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9561/ (Markdown: https://insights.sbomify.com/CVE-2026-9561/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9561
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9561
- OSV: https://osv.dev/vulnerability/CVE-2026-9561

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9561/
Summaries are generated and may contain mistakes; the official description above is the record.