CVE-2026-41699: Unsafe Deserialization in Spring GraphQL
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41699?
The severity of CVE-2026-41699 is rated as high with a score of 8.1.
How do I fix CVE-2026-41699?
To fix CVE-2026-41699, ensure that your application is updated to the latest version of VMware Spring for GraphQL that mitigates this vulnerability.
What types of attacks can CVE-2026-41699 enable?
CVE-2026-41699 can enable Remote Code Execution if exploited through malicious paginated GraphQL queries.
Which applications are affected by CVE-2026-41699?
CVE-2026-41699 affects applications using VMware Spring for GraphQL that process paginated GraphQL queries.
When was CVE-2026-41699 published?
CVE-2026-41699 was published on June 11, 2026.