CVE-2026-110724
Received Received - Intake

IP Spoofing Bypass in Eclipse Vert.x API Gateway

Publication date: 2026-10-15

Last updated on: 2026-10-15

Assigner: Eclipse Foundation

Description
In `api-gateway` versions till `1.7.3`, The default rate-limit key resolver, `ClientIpKeyResolver`, derives the per-client bucket key from the leftmost element of the `X-Forwarded-For` request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy list. A single attacker can therefore obtain an unlimited number of independent rate-limit buckets — one per unique header value — and completely bypass the gateway's request-rate limiting on every route that uses the shipped default configuration.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-15
Last Modified
2026-10-15
Generated
2026-10-15
AI Q&A
2026-10-15
EPSS Evaluated
N/A
NVD
CVE-2026-110724
EUVD
EUVD-2026-102029

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Eclipse Foundation Eclipse Connected Services Platform 1.1.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-269 The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the Eclipse Connected Services Platform api-gateway versions up to 1.7.3. The default rate-limit key resolver, ClientIpKeyResolver, uses the leftmost value of the X-Forwarded-For header to create rate-limiting buckets. Since this value is set by the client and not validated, an attacker can bypass rate limits by spoofing different header values to create unlimited buckets.

Detection Guidance

To detect this vulnerability, inspect HTTP request logs for the api-gateway component. Look for multiple unique values in the X-Forwarded-For header from the same client IP. Check if rate-limiting is bypassed by monitoring request counts per client. Verify if the ClientIpKeyResolver is enabled in the default configuration.

Impact Analysis

If you use the affected api-gateway versions with default settings, an attacker could send excessive requests by changing the X-Forwarded-For header value. This could overwhelm your backend systems, leading to denial of service or degraded performance for legitimate users.

Compliance Impact

This vulnerability allows an attacker to bypass rate-limiting mechanisms by spoofing the X-Forwarded-For header, potentially enabling denial-of-service attacks or excessive resource consumption. While not directly impacting GDPR or HIPAA compliance, such attacks could lead to service disruptions or unauthorized access, indirectly affecting availability requirements under these regulations.

Mitigation Strategies

Upgrade api-gateway to a version beyond 1.7.3 where the issue is fixed. Configure a trusted-proxy list to validate the X-Forwarded-For header. Replace the default ClientIpKeyResolver with a resolver that uses validated client IP addresses. Apply network-level rate-limiting as a temporary measure.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-110724. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart