Eclipse Jetty & Vert.x: 25 Vulnerabilities Disclosed in Security, Auth, and Data Handling Batch
A batch of 25 vulnerabilities, ranging from Medium to Critical, were disclosed for Eclipse Jetty and Vert.x on October 15, 2026, impacting security and data handling.

Key findings
- 25 CVEs disclosed for Eclipse Jetty and Vert.x within an 18-hour window on Oct 14-15, 2026.
- Critical and High severity vulnerabilities found in authentication, data handling, and network protocols.
- Eclipse Jetty issues include auth bypass, insecure credential storage, and case-sensitive host whitelisting.
- Eclipse Vert.x vulnerabilities involve unbounded data aggregation, deserialization, and decompression risks.
- Affected components include api-gateway, various Jetty security modules, and multiple Vert.x clients (MySQL, PostgreSQL, DB2, Redis, MSSQL).
On October 15, 2026, a significant batch of 25 vulnerabilities was disclosed across multiple Eclipse projects, primarily affecting Eclipse Jetty and Eclipse Vert.x. These vulnerabilities, disclosed within an 18-hour window, range in severity from Medium to Critical, with a notable concentration of High-severity issues. The disclosures highlight potential risks in areas such as authentication, request handling, and data processing, underscoring the need for users to update their Eclipse components to secure versions.
Several vulnerabilities in Eclipse Jetty relate to security constraint handling and authentication mechanisms. CVE-2026-19863, a Critical severity flaw, allows unauthenticated clients to access protected resources due to an unanchored substring match in the EthereumAuthenticator's login path detection. Similarly, CVE-2026-18659 (Medium) and CVE-2026-18662 (Medium) describe bypasses and improper handling of security constraints defined via HTTP methods and URL patterns in jetty-security and related modules. CVE-2026-19864 (Medium) points out that sensitive credentials, including plaintext passwords, could be persisted in session data stores if the credentials object is serializable. Additionally, CVE-2026-18660 (High) notes that the host whitelist/blacklist in jetty-server and jetty-proxy is case-sensitive, potentially allowing unintended hosts. Issues with HttpClient's handling of proxy authentication (CVE-2026-77711, High) and redirects (CVE-2026-76184, High) were also detailed.
The Eclipse Vert.x ecosystem is affected by a large number of vulnerabilities, many of which stem from inadequate size validation or improper handling of network protocols and data streams. CVE-2026-103224 (High) and CVE-2026-102462 (High) describe unbounded aggregation of network packets in MySQL and MSSQL clients, respectively, potentially leading to denial-of-service conditions. The Vert.x gRPC endpoint (CVE-2026-102475, High) and WebSocket implementation (CVE-2026-102467, High) are vulnerable to denial-of-service attacks due to unbounded decompression of compressed data. Unbounded deserialization of User Defined Type (UDT) data in the DB2 client (CVE-2026-102466, Critical) presents a significant risk. Other Vert.x vulnerabilities include unbounded array allocation in the MySQL client (CVE-2026-102464, High) and PostgreSQL client (CVE-2026-102463, High), and unbounded array allocation in the Redis client (CVE-2026-102465, High). CVE-2026-102461 (High) details an inefficient uniqueItems keyword validation in JSON processing, and CVE-2026-102479 (High) involves a header canonicalization issue in the HTTP/1.x decoder.
The api-gateway component is affected by three related vulnerabilities (CVE-2026-110724, CVE-2026-110723, both High; CVE-2026-110726, Medium) where the ClientIpKeyResolver uses the X-Forwarded-For header without proper validation, allowing clients to manipulate rate-limiting keys.
The majority of these vulnerabilities were patched in subsequent releases of the affected Eclipse projects. Users are strongly advised to consult the official Eclipse security advisories and update to the latest versions to mitigate these risks. The widespread nature of these disclosures across different components highlights the importance of maintaining up-to-date software dependencies within the Eclipse ecosystem.
The timely disclosure of these numerous vulnerabilities, particularly the critical and high-severity ones, underscores the ongoing security efforts within the Eclipse community and the importance of prompt patching for users. Staying informed about these disclosures and applying updates is crucial for maintaining the security posture of applications built on Eclipse technologies.
The batch also includes CVE-2026-110724, CVE-2026-110723, CVE-2026-110726, CVE-2026-19864, CVE-2026-19863, CVE-2026-18662, CVE-2026-18660, CVE-2026-18659, CVE-2026-77711, CVE-2026-76184, CVE-2026-76182, CVE-2026-18661, CVE-2026-103224, CVE-2026-103223, CVE-2026-102477, CVE-2026-102469, CVE-2026-102466, CVE-2026-102464, CVE-2026-102463, CVE-2026-102463, CVE-2026-102462, CVE-2026-102461, CVE-2026-102475, CVE-2026-102467, CVE-2026-102465, and CVE-2026-102479.