CVE-2026-110724

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.

Score

CVSS 3.1 7.5 High

Status

Awaiting Analysis - emo@eclipse.org

Published

2026-10-15

Last modified

2026-10-16

Weaknesses

CWE-269, CWE-639, CWE-863

Affected products

• Eclipse Connected Services Platform (Eclipse Foundation)

References

• https://github.com/eclipse-ecsp/api-gateway/pull/330
• https://gitlab.eclipse.org/security/cve-assignment/-/work_items/405
• https://github.com/eclipse-ecsp/api-gateway/security/advisories/GHSA-4j9j-mx7g-p9p6