CVE-2026-110723
Received Received - Intake

IP Spoofing Bypass in Eclipse Vert.x API Gateway

Publication date: 2026-10-15

Last updated on: 2026-10-15

Assigner: Eclipse Foundation

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-15
Last Modified
2026-10-15
Generated
2026-10-15
AI Q&A
2026-10-15
EPSS Evaluated
N/A
NVD
CVE-2026-110723
EUVD
EUVD-2026-102030

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
Eclipse Foundation Eclipse Connected Services Platform 1.1.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-644 The product does not neutralize or incorrectly neutralizes web scripting syntax in HTTP headers that can be used by web browser components that can process raw headers, such as Flash.
CWE-290 This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the api-gateway component in versions up to 1.7.3. The default rate-limit key resolver, ClientIpKeyResolver, uses the leftmost value of the X-Forwarded-For header to determine rate limits. Since this value can be spoofed by attackers and is not validated against a trusted-proxy list, an attacker can bypass rate limiting by providing multiple unique header values, creating unlimited rate-limit buckets.

Detection Guidance

Check if your api-gateway version is between 1.1.1 and 1.7.3. Inspect HTTP headers for X-Forwarded-For spoofing attempts by monitoring for multiple unique values in the leftmost position of the header.

Impact Analysis

If you use api-gateway versions 1.1.1 through 1.7.3 with default settings, an attacker could overwhelm your system by bypassing rate limits. This could lead to denial-of-service conditions, degraded performance, or increased resource consumption as the system processes excessive requests.

Mitigation Strategies
  • Upgrade api-gateway to a version beyond 1.7.3 where the issue is resolved.
  • Configure a trusted-proxy list to validate the X-Forwarded-For header values.
  • Replace the default ClientIpKeyResolver with a custom resolver that uses validated client IP addresses.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-110723. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart