Eclipse Connected Services Platform up to 1.7.3 Api Gateway ClientIpKeyResolver X-Forwarded-For authentication bypass

Summaryinfo

A vulnerability, which was classified as critical, has been found in Eclipse Connected Services Platform up to 1.7.3. Affected is the function ClientIpKeyResolver of the component Api Gateway. The manipulation of the argument X-Forwarded-For leads to authentication bypass. This vulnerability is uniquely identified as CVE-2026-110726. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Eclipse Connected Services Platform up to 1.7.3. This issue affects the function ClientIpKeyResolver of the component Api Gateway. The manipulation of the argument X-Forwarded-For with an unknown input leads to a authentication bypass vulnerability. Using CWE to declare the problem leads to CWE-288. A product requires authentication, but the product has an alternate path or channel that does not require authentication. Impacted is integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-110726 since 10/14/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/15/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Eclipse

Name

• Connected Services Platform

Version

• 1.7.0
• 1.7.1
• 1.7.2
• 1.7.3

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion