Quick answers
- Is CVE-2026-59285 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59285 being exploited in the wild.
- How severe is CVE-2026-59285?
- High severity, with a CVSS score of 8.1, published 27 August 2026.
- Which products and versions are affected?
- VMware Spring for GraphQL 2.0.0 to 2.0.4.
- Is there a fix for CVE-2026-59285?
- 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-59285 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59285?
- 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
The vulnerability is a unsafe deserialization flaw triggered during the processing of paginated GraphQL queries. The vulnerable component handles query pagination parameters without proper validation, allowing attackers to inject malicious serialized objects that execute arbitrary code upon deserialization. This is a network-reachable attack requiring the attacker to send crafted GraphQL queries to an affected endpoint; no authentication is typically required for GraphQL query execution. Successful exploitation results in remote code execution with the privileges of the application process. A patch is expected to address versions 2.0.0 through 2.0.4.
Affected products
- VMware Spring for GraphQL 2.0.0 to 2.0.4
Timeline
- 2026-08-27: disclosed