cve.bz

CVE-2026-110726 eclipse foundation eclipse connected services platform: Use of Less Trusted Source

6.5 mediumEPSS 0.2%

Medium (6.5) in eclipse foundation eclipse connected services platform. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 9th 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: no · 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-348 Use of Less Trusted Source
CWE-770 Allocation of Resources Without Limits or Throttling
CWE-807 Reliance on Untrusted Inputs in a Security Decision
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-110726 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110726?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110726?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-110726 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.

Affected

  • eclipse foundation:eclipse connected services platform

Versions

From the CNA's record in the CVE List.

ProductAffected
Eclipse Foundation Eclipse Connected Services Platformfrom 1.5.4 through 1.7.3

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as a Moderate impact because while an unauthenticated remote actor can evade traffic throttling by forging HTTP proxy headers, exploitation is limited to circumventing rate limits and does not allow unauthorized data disclosure or arbitrary code execution. The flaw only manifests in environments where routes rely on default client IP resolution without upstream proxy validation to restrict header injection. Red Hat enterprise offerings do not distribute the Eclipse ECSP api-gateway service, resulting in minimal overall risk to supported product environments.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-110726.

Attack patterns (CAPEC)

  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-141 Cache Poisoning Likelihood: High · Severity: High
  • CAPEC-142 DNS Cache Poisoning Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON