<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VulnFeed.org: Eclipse Foundation Eclipse Vert.x</title><link>https://vulnfeed.org/</link><description>Every disclosure, as it lands. Critical-only feed available.</description><language>en</language><atom:link href="https://vulnfeed.org/feed/product/eclipse-foundation-eclipse-vert-x.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-118487: Heap exhaustion via unbounded line accumulation in Vert.x STOMP FrameParser</title><link>https://vulnfeed.org/cve/CVE-2026-118487/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-118487/</guid><pubDate>Tue, 03 Nov 2026 15:27:18 +0000</pubDate><description>In Eclipse Vert.x versions [4.0.0, 4.5.35] or [5.0.0, 5.2.2], the `FrameParser` in vertx-stomp creates a `RecordParser` without setting `maxRecordSize`, so any peer that streams bytes continuously without a newline character causes the parser to accumulate data indefinitely. Both the STOMP server and the STOMP client are affected: a malicious server can exploit this against a connecting client, and a malicious client can exploit this against a server before or after authentication. Sustained byte streaming exhausts JVM heap memory, crashing the affected process and causing a complete denial of service.</description></item><item><title>CVE-2026-118489: CachingWebClient shares user-specific HTTP responses across users via the shared cache tier</title><link>https://vulnfeed.org/cve/CVE-2026-118489/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-118489/</guid><pubDate>Tue, 03 Nov 2026 14:55:48 +0000</pubDate><description>In Eclipse Vert.x versions [4.0.0,4.5.35] or [5.0.0,5.2.2], when one `CachingWebClient` is shared across users — the documented pattern of a per-user `WebClientSession` over a shared caching client — a response that is specific to one user but is cacheable and not marked `private`/`no-store` is stored in the client-level shared cache tier and served to other users requesting the same URL. A later user&apos;s session, or an anonymous caller through the same client, can receive an earlier user&apos;s response. Depending on the response this discloses authenticated content or a session cookie, the latter enabling session fixation or hijacking.</description></item></channel></rss>
