CVE-2026-110726CWE-348CWE-770CWE-807denial-of-service

CVE-2026-110726

Medium · published October 15, 2026

CVSS v3.1
6.5
EPSS
0%
Percentile
8.4
In the wild
Unconfirmed
What it 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 record
Technical detail
CVSS v3.1
6.5 · MEDIUM
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS v4.0
Not supplied
EPSS
0.00192 · 8.4th percentile
Weaknesses
CWE-348 · Use of Less Trusted Source; CWE-770 · Allocation of Resources Without Limits or Throttling; CWE-807 · Reliance on Untrusted Inputs in a Security Decision
Published
2026-10-15T16:16Z
References (3)
https://github.com/eclipse-ecsp/api-gateway/pull/330 · [email protected]https://github.com/eclipse-ecsp/api-gateway/security/advisories/GHSA-ch6x-rg7q-7jfx · [email protected]https://gitlab.eclipse.org/security/cve-assignment/-/work_items/404 · [email protected]
EPSS history
Timeline
  • 17 OCT 03:28Z
    EPSS moved — → 0%
    epss
  • 15 OCT 11:58Z
    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…
    cvelistv5
  • 15 OCT 11:58Z
    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…
    cvelistv5