# CVE-2026-59289: Spring for GraphQL Spring Data pagination denial of service

Source: https://junglewise.ai/threats/cve-2026-59289-spring-for-graphql-spring-data-pagination-denial-of-service  
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-59289 · Severity: high · CVSS 7.5 · Published 2026-08-27

Spring for GraphQL is a framework for building GraphQL APIs on Java. Its Spring Data pagination feature can be exploited through malicious queries to consume excessive memory or overload the database backend, causing service unavailability for legitimate users. An attacker can trigger these attacks remotely without authentication.

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-59289 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-59289 being exploited in the wild.

**How severe is CVE-2026-59289?** High severity, with a CVSS score of 7.5, published 27 August 2026.

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

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

**Am I affected by CVE-2026-59289?** 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 exists in Spring for GraphQL's pagination support for scrollable queries, which resolves client-supplied pagination arguments without sufficient validation and forwards them directly to the underlying Spring Data repository. An attacker can craft a GraphQL query with malicious pagination parameters to force the application to allocate excessive memory or generate resource-intensive database queries, resulting in denial of service. The attack is network-accessible and requires no authentication. Patches are available in Spring for GraphQL 1.4.7, 1.3.10, and 2.0.5 or later.

## Affected products

- VMware Spring for GraphQL 1.2.0–1.3.9, 1.4.0–1.4.6, 2.0.0–2.0.4

## Timeline

- 2026-08-27: disclosed

## References

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

## Related threats

- [Spring for GraphQL denial of service with WebSocket keepAlive](https://junglewise.ai/threats/cve-2026-59287-spring-for-graphql-denial-of-service-with-websocket-keepalive)
- [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)