# CVE-2026-59287: Spring for GraphQL denial of service with WebSocket keepAlive

Source: https://junglewise.ai/threats/cve-2026-59287-spring-for-graphql-denial-of-service-with-websocket-keepalive  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-27. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-59287 · Severity: medium · CVSS 5.9 · Published 2026-08-27

Spring for GraphQL is a framework component used to build GraphQL APIs in Spring applications. When WebSocket connections are enabled with keepAlive functionality, an attacker can send specially crafted requests to exhaust server resources and cause service unavailability for legitimate users.

Technologies: [VMware Spring for GraphQL](https://junglewise.ai/threats/technologies/spring-for-graphql). Vendors: [VMware](https://junglewise.ai/threats/vendors/vmware).

## Quick answers

**Is CVE-2026-59287 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-59287 being exploited in the wild.

**How severe is CVE-2026-59287?** Medium severity, with a CVSS score of 5.9, published 27 August 2026.

**Which products and versions are affected?** VMware Spring for GraphQL 1.3.0 through 1.3.9, 1.4.0 through 1.4.6, 2.0.0 through 2.0.4.

**Is there a fix for CVE-2026-59287?** 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-59287 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-59287?** 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 a denial of service flaw in Spring for GraphQL's WebSocket client implementation when keepAlive is enabled. The vulnerability allows an attacker with network access to send crafted WebSocket frames that trigger resource exhaustion or infinite loops in the keepAlive handling logic. No authentication is required to exploit this vulnerability as WebSocket connections can be initiated by unauthenticated clients. An attacker can leverage this to crash the GraphQL service or degrade performance, impacting availability. Patches are available in updated versions of Spring for GraphQL.

## Affected products

- VMware Spring for GraphQL 1.3.0 through 1.3.9, 1.4.0 through 1.4.6, 2.0.0 through 2.0.4

## Timeline

- 2026-08-27: disclosed

## References

- [https://spring.io/security/cve-2026-59287](https://spring.io/security/cve-2026-59287)

## Related threats

- [Spring for GraphQL Spring Data pagination denial of service](https://junglewise.ai/threats/cve-2026-59289-spring-for-graphql-spring-data-pagination-denial-of-service)
- [Spring for GraphQL missing Subresource Integrity on CDN-loaded JavaScript](https://junglewise.ai/threats/cve-2026-59286-spring-for-graphql-missing-subresource-integrity-on-cdn-loaded)
- [Spring for GraphQL unsafe deserialization in pagination](https://junglewise.ai/threats/cve-2026-59285-spring-for-graphql-unsafe-deserialization-in-pagination)
- [VMware Spring for GraphQL authorization bypass in @Controller data fetchers](https://junglewise.ai/threats/cve-2026-41856-vmware-spring-for-graphql-authorization-bypass-in-controller-data)
- [VMware Spring for GraphQL Cross-Site WebSocket Hijacking](https://junglewise.ai/threats/cve-2026-41700-vmware-spring-for-graphql-cross-site-websocket-hijacking)