Read the docs
TI-2026-74753 Aliases CVE-2026-110724GHSA-qx92-7q4c-w2x8

Rate-limit bypass in api-gateway via spoofed X-Forwarded-For header

Priority LOW 39CWE-269Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Privilege escalation, Security bypass
Confidentiality · integrity · availability
None · High · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-269 and CWE-639.

Summary

Eclipse Connected Services Platform from 1.1.1 through 1.7.3 contains a flaw in the api-gateway default rate-limit key resolver, ClientIpKeyResolver. It derives the client bucket key from the leftmost X-Forwarded-For header value without checking that value against a trusted proxy list (CWE-639). An unauthenticated remote attacker can send a different header value with each request to obtain a new rate-limit bucket each time, bypassing request-rate limiting on routes that use the shipped default configuration.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00272 19th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Eclipse FoundationEclipse Connected Services Platform1.1.1 – 1.7.3—No fix listedCNA
  • Eclipse Connected Services Platform VendorEclipse Foundation Affected 1.1.1 – 1.7.3 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for Eclipse Connected Services Platform.

Written with Claude Haiku 5.5 from the sources below · 2026-11-06

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-10-16 Threatist record created from CVE-2026-110724
  2. 2026-10-16 CVSS score added · CISA ADP
  3. 2026-10-16 CISA SSVC decision points changed
  4. 2026-10-18 Alias added: GHSA-qx92-7q4c-w2x8
  5. 2026-11-06 Affected versions changed · Red Hat
  6. 2026-11-06 CVSS score added · Red Hat

References

Other 3

  • TI-2023-23979 The HTTP/2 protocol allows a denial of service (server resource consumption) because… KEVCVSS 3.1HIGH 7.5
  • TI-2026-81947 Unauthenticated command injection in Eclipse Che che-machine-exec CVSS 3.1CRITICAL 9.8
  • TI-2026-13216 CWE-863: ABAC authorization bypass via trailing slash route normalization in Eclipse BaSyx Go Components CVSS 3.1CRITICAL 9.8
  • TI-2026-06514 Path traversal in Eclipse BaSyx CVSS 3.1CRITICAL 10.0
  • TI-2026-01382 In the Eclipse Theia Website repository, the GitHub Actions workflow… CVSS 3.1CRITICAL 10.0
  • TI-2026-74697 Authentication bypass in Eclipse Jetty EthereumAuthenticator CVSS 4.0CRITICAL 9.3
See all 466 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences