Loading vulnerability…
CVE-2026-59285 is an unsafe deserialization vulnerability in Spring for GraphQL affecting pagination support. The issue arises when a Spring for GraphQL application processes paginated GraphQL queries and deserializes attacker-controlled JSON data through Jackson 2.x in an unsafe manner. Under the documented conditions, a maliciously crafted GraphQL request can trigger deserialization of attacker-influenced types and lead to remote code execution. The vulnerability is specifically associated with applications that expose paginated GraphQL fields and have deserializable classes present that can be abused as part of a gadget chain or equivalent deserialization path.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.