Medium · CVSS 6.5CVE-2026-110726

CISA ADP VulnrichmentCVE-2026-110726

Answer in brief

CVE-2026-110726 records a Medium severity (CVSS 6.5) vulnerability in CISA ADP Vulnrichment. The current sources do not mark it as known exploited. The current feed maps Eclipse Foundation/Eclipse Connected Services Platform (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 15, 2026Updated Oct 15, 2026Source checked Oct 15, 2026First seen by HOL Oct 15, 2026Material review Oct 15, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.5
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Eclipse Foundation/Eclipse Connected Services Platform (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Eclipse Foundation/Eclipse Connected Services Platformgeneric	>=1.5.4 <=1.7.3	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Eclipse Foundation/Eclipse Connected Services Platform.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 15, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.