CVE-2026-59285: Spring for GraphQL applications are vulnerable to Unsafe Deserialization when processing paginated GraphQL que

This month

HIGH 8.1REMOTEUPGRADE

CVE-2026-59285 is a high-severity flaw (CVSS 8.1) affecting spring for graphql. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Spring for GraphQL applications are vulnerable to Unsafe Deserialization when processing paginated GraphQL queries. Spring for GraphQL 2.0.0 - 2.0.4

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 62%)
CISA exploited list	No
Weakness	CWE-502
Published	2026-08-27
Last modified	2026-09-02

Publisher (CNA): VMware · Vendor: vmware

Last updated 2026-09-02 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-08-27 20:17 UTCPublished CVE record published
2026-09-02 19:17 UTCUpdated Record last modified

vmware spring for graphql UPGRADE

Affected: >= 2.0.0 and < 2.0.4.1

Fixed in: 2.0.4.1

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy spring-for-graphql || rpm -q spring-for-graphql || spring-for-graphql --version

2. UPGRADE to 2.0.4.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-for-graphql

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-for-graphql

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison spring-for-graphql sudo apt install spring-for-graphql=<VERSION_BEFORE_2.0.0> sudo apt-mark hold spring-for-graphql

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spring-for-graphql sudo dnf downgrade spring-for-graphql-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add spring-for-graphql

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-59285?

spring for graphql: upgrade to 2.0.4.1. Exact commands for each OS are on this page.

Is CVE-2026-59285 being exploited?

CVE-2026-59285 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-59285 affect?

CVE-2026-59285 affects spring for graphql. Severity is high (CVSS 8.1). Spring for GraphQL applications are vulnerable to Unsafe Deserialization when processing paginated GraphQL queries. Spring for GraphQL 2.0.0 - 2.0.4

How urgent is CVE-2026-59285?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

Software pages

VMware vulnerabilities

Related CVEs

CVE-2026-59286 HIGH 8.1 UPGRADE The GraphiQL page bundled with Spring for GraphQL loads JavaScript libraries from a public CDN, without Subres
CVE-2026-59289 HIGH 7.5 UPGRADE Spring for GraphQL's Spring Data pagination support resolves arguments of a scrollable query and forwards the
CVE-2026-59287 MEDIUM 5.9 UPGRADE Spring for GraphQL is vulnerable to Denial of Service attacks when using the WebSocket client with keepAlive e
CVE-2026-59288 HIGH 7.4 UPGRADE The GraphiQL page bundled with Spring for GraphQL sends requests to the GraphQL endpoints of the application

References

← Back to latest CVEs