Skip to content
OpenAdvisories
Medium · 6.5 CVE-2026-110726 EUVD-2026-102022GHSA-r566-6hq2-633r

In `api-gateway` versions till `1.7.3`, The default rate-limit key resolver, `ClientIpKeyResolver`, derives the per-client bucket key from …

Published Oct 15, 2026 · Updated Oct 15, 2026 · Assigned by eclipse

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.

Affected products

VendorProductAffectedFixed
Eclipse Foundation Eclipse Connected Services Platform 1.5.4 – ≤ 1.7.3 —

References