Quick answers
- Is CVE-2026-59279 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59279 being exploited in the wild.
- How severe is CVE-2026-59279?
- High severity, with a CVSS score of 7.5, published 21 August 2026.
- Which products and versions are affected?
- VMware Spring Ai 2.0.0.
- Is there a fix for CVE-2026-59279?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-59279 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59279?
- Check whether you run VMware Spring Ai at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The MCP Streamable HTTP server transport (WebFlux and WebMvc variants) in Spring AI fails to implement session limits and permits unauthenticated access by default. A remote attacker can exploit this by repeatedly initiating new sessions without authentication, causing unbounded accumulation of session state in memory. As sessions persist without expiration or eviction policy, available heap memory is gradually exhausted, triggering out-of-memory conditions and ultimately a denial of service affecting all clients. The vulnerability requires only network reachability to the affected service and no authentication credentials. A patch implementing session limits and authentication requirements is expected from the vendor.
Affected products
- VMware Spring AI 2.0.0
Timeline
- 2026-08-21: published