Quick answers
- Is CVE-2026-59291 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59291 being exploited in the wild.
- How severe is CVE-2026-59291?
- Low severity, with a CVSS score of 2, published 27 August 2026.
- Which products and versions are affected?
- VMware Spring Cloud Function 4.2.0–4.2.7, 4.3.0–4.3.4, 5.0.0–5.0.3.
- Is there a fix for CVE-2026-59291?
- 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-59291 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59291?
- Check whether you run VMware Spring Cloud Function 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
This vulnerability in Spring Cloud Function allows arbitrary file read and server-side request forgery (SSRF) attacks. The exact attack vector and vulnerable component are not fully detailed in the advisory reference material provided, but the issue affects multiple versions: 5.0.0–5.0.3, 4.3.0–4.3.4, and 4.2.0–4.2.7. The vulnerability is likely network-reachable and may require specific request manipulation or function invocation. Attackers can exploit this to access sensitive files on the server filesystem or trigger requests to internal resources.
Affected products
- VMware Spring Cloud Function 4.2.0–4.2.7, 4.3.0–4.3.4, 5.0.0–5.0.3
Timeline
- 2026-08-27: disclosed