Eclipse Connected Services Platform up to 1.7.3 api-gateway ClientIpKeyResolver inclusion of web functionality from an untrusted source

Summaryinfo

A vulnerability was found in Eclipse Connected Services Platform up to 1.7.3. It has been classified as critical. This vulnerability affects the function ClientIpKeyResolver of the component api-gateway. Performing a manipulation results in inclusion of web functionality from an untrusted source. This vulnerability is identified as CVE-2026-110724. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Eclipse Connected Services Platform up to 1.7.3. It has been classified as critical. This affects the function ClientIpKeyResolver of the component api-gateway. The manipulation with an unknown input leads to a inclusion of web functionality from an untrusted source vulnerability. CWE is classifying the issue as CWE-830. The product includes web functionality (such as a web widget) from another domain, which causes it to operate within the domain of the product, potentially granting total access and control of the product to the untrusted source. This is going to have an impact on 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. This vulnerability is uniquely identified as CVE-2026-110724 since 10/14/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for 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.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-102029). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion