CVE-2026-110726
Received Received - Intake

Rate Limiting Bypass via X-Forwarded-For in 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-110726
EUVD
EUVD-2026-102022

Affected Vendors & Products

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

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-807 The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism.
CWE-348 The product has two different sources of the same data or information, but it uses the source that has less support for verification, is less trusted, or is less resistant to attack.
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

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 determine rate limits. Since this header value is client-supplied and not validated against a trusted-proxy list, an attacker can bypass rate limiting by spoofing multiple unique header values, creating unlimited rate-limit buckets.

Detection Guidance

Check if your api-gateway version is between 1.5.4 and 1.7.3. Monitor HTTP headers for unusual patterns in the X-Forwarded-For field, such as multiple unique values from the same client. Inspect rate-limit logs for bypass attempts where the same client bypasses limits by spoofing different header values.

Impact Analysis

An attacker could exploit this to send unlimited requests to the API gateway, overwhelming backend services. This could lead to denial of service, degraded performance, or potential abuse of API resources. Systems relying on rate limiting for security or performance would be particularly affected.

Mitigation Strategies

Upgrade api-gateway to a version beyond 1.7.3. 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.

Chat Assistant

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

EPSS Chart