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.
Severity
CVSS 3.1
7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3%(unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-290Authentication Bypass by Spoofing CWE-644Improper Neutralization of HTTP Headers for Scripting Syntax
Show the promptExplain CVE-2026-110723 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110723?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110723?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-110723 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Eclipse Foundation Eclipse Connected Services Platform
from 1.1.1 through 1.7.3
Red Hat
Red Hat rates this Moderate.
Red Hat's statement
This vulnerability is rated as Moderate severity because while an unauthenticated remote adversary can circumvent request throttling, the flaw does not facilitate arbitrary code execution or compromise sensitive data. In environments operating this gateway service, spoofed proxy forwarding headers allow clients to establish arbitrary tracking buckets, potentially resulting in resource exhaustion or denial of service against underlying backend systems. Eclipse Connected Services Platform api-gateway is not distributed or enabled in supported Red Hat enterprise offerings.