CVE-2026-41699 Unsafe Deserialization in Spring GraphQL
Attackers can achieve remote code execution via malicious GraphQL requests in Spring for GraphQL applications exposing paginated fields.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-41699?
CVE-2026-41699 is a high-severity unsafe deserialization vulnerability in Spring for GraphQL, published on 11 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Spring for GraphQL applications are vulnerable to Unsafe Deserialization when processing paginated GraphQL queries. An attacker can craft a malicious GraphQL request that can lead to Remote Code Execution when the application exposes a paginated (Connection) field and the classpath contains specific classes that can be leveraged during deserialization.
Affected versions: Spring for GraphQL 2.0.0 through 2.0.3; 1.4.0 through 1.4.5; 1.3.0 through 1.3.8.
Weakness: CWE-502
Which versions are affected by CVE-2026-41699?
6 open source packages ship an affected version, including org.springframework.graphql:spring-graphql. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.springframework.graphql:spring-graphql Maven | From 1.3.0 to 1.3.8 | None |
org.springframework.graphql:spring-graphql Maven | From 1.3.0 to 1.3.8 | None |
org.springframework.graphql:spring-graphql Maven | From 1.4.0 | 1.4.6 |
org.springframework.graphql:spring-graphql Maven | From 1.4.0 | 1.4.6 |
org.springframework.graphql:spring-graphql Maven | From 2.0.0 | 2.0.4 |
org.springframework.graphql:spring-graphql Maven | From 2.0.0 | 2.0.4 |
Products include Vmware Spring for Graphql.
How do I fix CVE-2026-41699?
Upgrade org.springframework.graphql:spring-graphql to a fixed version for your release line: 1.4.6 or 2.0.4.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2026-41699 being exploited?
There is no known exploitation of CVE-2026-41699 in the wild and no public exploit code.
Other vulnerabilities in Spring for GraphQL
- CVE-2026-59285 Spring for GraphQL Unsafe Deserialization in pagination support
- CVE-2026-59286 Spring for GraphQL loads Untrusted Resources in GraphiQL support
- CVE-2026-41700 Cross-Site WebSocket Hijacking in Spring for GraphQL
- CVE-2026-59288 Spring for GraphQL Information Exposure in GraphiQL support
- CVE-2026-59289 Spring for GraphQL Denial of Service via pagination support
Sources
Also known as GHSA-px92-q6rc-6mwv, ROOT-APP-MAVEN-CVE-2026-41699.