Quick answers
- Is CVE-2026-59286 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59286 being exploited in the wild.
- How severe is CVE-2026-59286?
- High severity, with a CVSS score of 8.1, published 27 August 2026.
- Which products and versions are affected?
- VMware Spring for GraphQL 1.0.0–1.0.7, 1.1.0–1.3.9, 1.4.0–1.4.6, 2.0.0–2.0.4.
- Is there a fix for CVE-2026-59286?
- 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-59286 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59286?
- Check whether you run VMware Spring for GraphQL 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 is an integrity validation bypass in which the GraphiQL page references external JavaScript libraries from public CDNs without implementing Subresource Integrity (SRI) checks. The absence of SRI checksums allows a man-in-the-middle attacker, DNS hijacker, or compromised CDN to serve malicious JavaScript that will execute with the privileges of the authenticated user accessing the GraphiQL page. No authentication or special network position is strictly required if the attacker can influence the HTTP response. The vulnerability affects Spring for GraphQL versions 1.0.0 through 2.0.4 across multiple minor version branches. Patches to add SRI validation are expected from the vendor.
Affected products
- VMware Spring for GraphQL 1.0.0–1.0.7, 1.1.0–1.3.9, 1.4.0–1.4.6, 2.0.0–2.0.4
Timeline
- 2026-08-27: disclosed