All reports
High

io.vertx/vertx-web-client: vertx-web-client: Information disclosure via shared web client cache

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-118489

Probability of exploitation in the next 30 days: 0.34%

FIRST EPSS · 2026-11-20

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's session, or an anonymous caller through the same client, can receive an earlier user's response. Depending on the response this discloses authenticated content or a session cookie, the latter enabling session fixation or hijacking.

A flaw was found in Eclipse Vert.x Web Client. When a caching client is shared across multiple user sessions, responses intended for a specific user that are not explicitly marked as private are stored in a shared cache. Consequently, an unauthorized user or caller requesting the same resource can receive the previously cached response, leading to sensitive information disclosure. This flaw can expose authentication cookies or confidential user data, potentially enabling session hijacking.