CVE-2026-41699 is an unsafe deserialization vulnerability in Spring for GraphQL processing of paginated GraphQL queries. A malicious GraphQL request can cause unintended type instantiation or deserialization when an application exposes a paginated Connection field and its runtime classpath contains classes usable during deserialization. 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 releases in those ranges.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical unsafe-deserialization vulnerability in Spring for GraphQL that can permit unauthenticated remote code execution through malicious paginated GraphQL requests, contingent on an exposed Connection field and exploitable classes being present on the application classpath.
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 with remote code execution potential mentioned as part of the same coordinated Spring security release.
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.