CVE-2026-9561: High severity Eclipse Kura vulnerability

Published Jul 14, 2026
·
Updated

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.

Affected Software

2 affected components
Eclipse Kura<5.6.2
Eclipse Kura>=5.0.0<5.6.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Eclipse Kura to a version that resolves this vulnerability.

    Fixed in 5.6.2
  2. Configuration

    Stop using the client-supplied X-Forwarded-For HTTP header as the authoritative source of the client IP address in audit log entries; initialize audit context using a trusted IP source instead.

    Eclipse Kura Web Console / REST API (org.eclipse.kura.web2, org.eclipse.kura.rest.provider) Trust of client-supplied X-Forwarded-For = Do not trust X-Forwarded-For as authoritative client IP for audit context
  3. Configuration

    Avoid unconditionally installing Jetty ForwardedRequestCustomizer on all HTTP/HTTPS connectors; configure it so HttpServletRequest.getRemoteAddr() does not reflect attacker-controlled forwarded header values.

    Eclipse Kura Jetty customizer (org.eclipse.kura.jetty.customizer) ForwardedRequestCustomizer installation = Install conditionally (or not unconditionally)

Event History

Jul 14, 2026
CVE Published
via MITRE·07:59 AM
Data Sourced
via MITRE·07:59 AM
DescriptionWeakness
Data Sourced
via NVD·09:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 4, 58624
Event
via FIRST·11:52 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-9561?

CVE-2026-9561 has a risk score of 45, indicating a moderate severity level.

2

How do I fix CVE-2026-9561?

To address CVE-2026-9561, upgrade to Eclipse Kura version 5.6.2 or later.

3

What components are affected by CVE-2026-9561?

CVE-2026-9561 affects the org.eclipse.kura.web2 and org.eclipse.kura.rest.provider components.

4

What is the impact of exploiting CVE-2026-9561?

Exploiting CVE-2026-9561 can allow an attacker to manipulate audit log entries by spoofing the client IP address.

5

When was CVE-2026-9561 published?

CVE-2026-9561 was published on July 14, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203