CVE-2026-118489

CachingWebClient shares user-specific HTTP responses across users via the shared cache tier

  • High 7.5

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.

Key facts

Published
3 Nov 2026
Last changed
3 Nov 2026
Assigned by
eclipse
EPSS
0.342% likely to be exploited in the next 30 days, higher than 28.122% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: yes; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.5CVSS 3.1, Highfrom the CNA (eclipse)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Eclipse FoundationEclipse Vert.x
  • Default status: unaffected
  • 4.0.0 up to and including 4.5.35 (affected)
  • 5.0.0 up to and including 5.2.2 (affected)

Timeline

  1. 3 Nov 2026 Published

Weakness

References