# CVE-2026-59287: Spring for GraphQL WebSocket Client Denial of Service

> Attackers can cause denial of service in Spring for GraphQL applications using WebSocket clients with keepAlive enabled.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Aug 2026
- **Updated:** 2 Sep 2026
- **Also known as:** CLSA-2026-1791367893, CLSA-2026-1791825433, CLSA-2026-1791827348, GHSA-ch79-c8j8-qqf6

## What is CVE-2026-59287?

CVE-2026-59287 is a medium-severity denial of service vulnerability in Spring for GraphQL, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Spring for GraphQL is vulnerable to Denial of Service attacks when using the WebSocket client with keepAlive enabled.
Spring for GraphQL 2.0.0 - 2.0.4
Spring for GraphQL 1.4.0 - 1.4.6
Spring for GraphQL 1.3.0 - 1.3.9

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-59287?

It affects 1 product.


Products: Vmware Spring for Graphql.

## How do I fix CVE-2026-59287?

Upgrade to a fixed version.

## Is CVE-2026-59287 being exploited?

There is no known exploitation of CVE-2026-59287 in the wild and no public exploit code.

## Other vulnerabilities in Spring for GraphQL

- [CVE-2026-59285](https://insights.sbomify.com/CVE-2026-59285/): Spring for GraphQL Unsafe Deserialization in pagination support (high 8.1)
- [CVE-2026-59286](https://insights.sbomify.com/CVE-2026-59286/): Spring for GraphQL loads Untrusted Resources in GraphiQL support (high 8.1)
- [CVE-2026-41699](https://insights.sbomify.com/CVE-2026-41699/): Unsafe Deserialization in Spring GraphQL (high 8.1)
- [CVE-2026-41700](https://insights.sbomify.com/CVE-2026-41700/): Cross-Site WebSocket Hijacking in Spring for GraphQL (high 8.1)
- [CVE-2026-59288](https://insights.sbomify.com/CVE-2026-59288/): Spring for GraphQL Information Exposure in GraphiQL support (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59287 and fix it if it is affected.

What it is: CVE-2026-59287 is a medium-severity denial of service vulnerability in Spring for GraphQL, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59287 in the wild and no public exploit code.

Affected product: Spring for GraphQL. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59287/ (Markdown: https://insights.sbomify.com/CVE-2026-59287/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59287
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59287
- OSV: https://osv.dev/vulnerability/CVE-2026-59287

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59287/
Summaries are generated and may contain mistakes; the official description above is the record.