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.
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Thu, 15 Oct 2026 13:30:00 +0000

Type Values Removed Values Added
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.
Weaknesses CWE-290
CWE-644
References

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: eclipse

Published:

Updated: 2026-10-15T13:11:12.574Z

Reserved: 2026-10-14T14:52:28.420Z

Link: CVE-2026-110723

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-15T13:17:12.857

Modified: 2026-10-15T13:17:12.857

Link: CVE-2026-110723

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses