# CVE-2026-110723: Security feature bypass in Eclipse Connected Services Platform

> Attackers can bypass rate limiting in Eclipse API Gateway by spoofing the X-Forwarded-For header to create unlimited independent buckets.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-9vqw-hvjv-fxx3, GHSA-m468-w7pr-f39w

## What is CVE-2026-110723?

CVE-2026-110723 is a high-severity vulnerability in Eclipse Connected Services Platform, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-644 (Improper Neutralization of HTTP Headers for Scripting Syntax), CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2026-110723?


## How do I fix CVE-2026-110723?

No fix has been published for CVE-2026-110723 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110723 being exploited?

There is no known exploitation of CVE-2026-110723 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110723 and fix it if it is affected.

What it is: CVE-2026-110723 is a high-severity vulnerability in Eclipse Connected Services Platform, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110723 in the wild and no public exploit code.

Affected product: Eclipse Connected Services Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110723/ (Markdown: https://insights.sbomify.com/CVE-2026-110723/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110723
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110723
- OSV: https://osv.dev/vulnerability/CVE-2026-110723

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110723/
Summaries are generated and may contain mistakes; the official description above is the record.