CVE-2026-41699
Spring · Spring for GraphQL
Spring for GraphQL applications are vulnerable to unsafe deserialization during the processing of paginated queries, which can lead to remote code execution.
Executive summary
A high-severity unsafe deserialization vulnerability in Spring for GraphQL allows attackers to achieve remote code execution through malicious paginated queries.
Vulnerability
The application is vulnerable to unsafe deserialization when processing paginated GraphQL queries. An attacker can craft a malicious request that triggers the execution of arbitrary code if the application environment includes specific exploitable classes.
Business impact
A CVSS score of 8.1 indicates a high risk of total system compromise. If exploited, an attacker could achieve remote code execution (RCE), potentially resulting in full system takeover, data exfiltration, or the deployment of ransomware within the application environment.
Remediation
Immediate Action: Update to the patched versions: 2.0.4, 1.4.6, or 1.3.9, depending on the current version in use.
Proactive Monitoring: Monitor GraphQL request logs for unusual or malformed queries, particularly those related to pagination (Connection fields).
Compensating Controls: Implement a Web Application Firewall (WAF) with rules to inspect and filter suspicious GraphQL payloads and restrict input to trusted sources.
Exploitation status
Public Exploit Available: False
Analyst recommendation
Developers and system administrators should immediately update all instances of Spring for GraphQL to the latest secure versions. Review the application classpath to identify and remove any unnecessary classes that could be leveraged in a deserialization attack.