Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sat, 17 Oct 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 16 Oct 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Rate Limiting Bypass via Untrusted X‑Forwarded‑For Header in Eclipse Connected Services Platform API Gateway |
Fri, 16 Oct 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
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-269 CWE-639 CWE-863 |
|
| References |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: eclipse
Published:
Updated: 2026-10-16T18:43:57.741Z
Reserved: 2026-10-14T14:53:22.659Z
Link: CVE-2026-110724
Updated: 2026-10-16T18:42:25.375Z
Status : Awaiting Analysis
Published: 2026-10-15T13:17:12.973
Modified: 2026-10-16T19:17:03.597
Link: CVE-2026-110724
No data.
OpenCVE Enrichment
Updated: 2026-10-16T22:00:16Z