CVE-2026-110723CWE-290CWE-644

CVE-2026-110723

High · published October 15, 2026

CVSS v3.1
7.5
EPSS
0%
Percentile
25.9
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
7.5 · HIGH
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS v4.0
Not supplied
EPSS
0.00337 · 25.9th percentile
Weaknesses
CWE-290 · Authentication Bypass by Spoofing; CWE-644 · Improper Neutralization of HTTP Headers for Scripting Syntax
Published
2026-10-15T17:17Z
References (3)
https://github.com/eclipse-ecsp/api-gateway/pull/330 · [email protected]https://github.com/eclipse-ecsp/api-gateway/security/advisories/GHSA-m468-w7pr-f39w · [email protected]https://gitlab.eclipse.org/security/cve-assignment/-/work_items/406 · [email protected]
EPSS history
Timeline
  • 17 OCT 03:28Z
    EPSS moved — → 0%
    epss
  • 15 OCT 12:14Z
    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 12:14Z
    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