Unsafe Deserialization RCE in Spring for GraphQL paginated queries
CVE-2026-41699 is a high-severity unsafe deserialization vulnerability in Spring for GraphQL. The issue occurs when Spring for GraphQL processes paginated GraphQL queries involving a paginated Connection field and improperly allows deserialization or instantiation of attacker-controlled types during object translation. If the target application exposes such a paginated field and its classpath contains specific classes that can be abused during deserialization, a remote attacker can send a crafted GraphQL request that triggers unintended object construction and may result in remote code execution. Affected versions are Spring for GraphQL 2.0.0 through 2.0.3, 1.4.0 through 1.4.5, and 1.3.0 through 1.3.8, including unsupported versions in those ranges.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical unsafe deserialization vulnerability in Spring GraphQL framework infrastructure that can allow unauthenticated remote code execution via crafted HTTP request payloads.
An unsafe deserialization vulnerability in Spring for GraphQL that can allow remote code execution via malicious paginated GraphQL queries under specific application and classpath conditions.
An unsafe deserialization vulnerability in Spring for GraphQL affecting paginated GraphQL queries that can lead to remote code execution when specific conditions are met.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.