CVE-2026-59289

Spring for GraphQL Denial of Service via pagination support

Published Aug 27, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Spring for GraphQL's Spring Data pagination support resolves arguments of a scrollable query and forwards the client-supplied values to the underlying repository. An attacker can forge a malicious query for a Connection field that can exhaust application memory or place significant, prolonged load on the underlying datastore, resulting in a Denial of Service.
Spring for GraphQL 2.0.0 - 2.0.4
Spring for GraphQL 1.4.0 - 1.4.6
Spring for GraphQL 1.2.0 - 1.3.9

Analysis

AI-generated

Technical impact

Spring for GraphQL’s pagination handling can be manipulated by an attacker who crafts a malicious Connection field query. The framework forwards client‑supplied pagination values directly to the underlying repository, allowing an attacker to exhaust application memory or impose a prolonged, heavy load on the datastore. The result is a Denial of Service that leads to loss of availability for legitimate users.

Affected Systems

The vulnerability affects Spring for GraphQL versions 2.0.0 through 2.0.4, 1.4.0 through 1.4.6, and 1.2.0 through 1.3.9. These are distributed by the Spring project and used in Spring‑based GraphQL applications.

Risk and Exploitability

No public exploit has been reported and the EPSS score indicates a less than 1% likelihood of exploitation. The weakness is a classic resource‑exhaustion flaw (CWE‑770) that can be triggered via the exposed GraphQL endpoint; an attacker only needs the ability to send crafted queries to the service. The CVSS score of 7.5 signifies high severity, and while the lack of KEV listing suggests it is not actively exploited, denial of service can still have significant business impact, keeping the overall risk moderate to high.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Spring for GraphQL to a non‑vulnerable release.
  • If an immediate upgrade is not feasible, enforce strict limits on client‑supplied pagination arguments such as bounding page size or total result limits.
  • Monitor application memory and datastore performance for sudden spikes, and apply rate‑limiting or circuit‑breaker patterns to the GraphQL endpoint.

Generated by OpenCVE AI on September 1, 2026 at 01:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-399
CWE-400
Type Values Removed Values Added
First Time appeared Vmware
Vmware spring For Graphql
Weaknesses CWE-770
CPEs cpe:2.3:a:vmware:spring_for_graphql:*:*:*:*:*:*:*:*
Vendors & Products Vmware
Vmware spring For Graphql
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
Weaknesses CWE-399
CWE-400
Type Values Removed Values Added
First Time appeared Spring
Spring spring For Graphql
Vendors & Products Spring
Spring spring For Graphql
Type Values Removed Values Added
Description Spring for GraphQL's Spring Data pagination support resolves arguments of a scrollable query and forwards the client-supplied values to the underlying repository. An attacker can forge a malicious query for a Connection field that can exhaust application memory or place significant, prolonged load on the underlying datastore, resulting in a Denial of Service. Spring for GraphQL 2.0.0 - 2.0.4 Spring for GraphQL 1.4.0 - 1.4.6 Spring for GraphQL 1.2.0 - 1.3.9
Title Spring for GraphQL Denial of Service via pagination support
References
Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Sep 2, 2026, 4:29 PM
Reserved
Jul 4, 2026, 6:13 PM
Status
Modified
Published
Aug 27, 2026, 8:17 PM
Modified
Sep 2, 2026, 5:17 PM