Cross-Site WebSocket Hijacking in Spring for GraphQL
CVE-2026-41700 is a Cross-Site WebSocket Hijacking (CSWSH) vulnerability in Spring for GraphQL affecting applications that have the GraphQL WebSocket transport enabled. The issue allows a malicious website to establish or abuse a WebSocket connection in the context of an authenticated victim and execute arbitrary GraphQL operations using that victim’s session. Based on the provided content, exploitation is possible where the application relies on cookie-based session authentication and does not implement custom Spring Security WebSocket-level Origin enforcement. Affected versions are Spring for GraphQL 2.0.0 through 2.0.3, 1.4.0 through 1.4.5, 1.3.0 through 1.3.8, and 1.0.0 through 1.0.6.
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.
An authentication/session validation weakness in Spring GraphQL responsive query components that enables cross-site WebSocket hijacking and arbitrary operations.
A Cross-Site WebSocket Hijacking vulnerability in Spring for GraphQL applications with WebSocket transport enabled, allowing an attacker to induce an authenticated user to visit a malicious page and execute arbitrary GraphQL operations using the victim's credentials.
A cross-site WebSocket hijacking vulnerability in Spring for GraphQL affecting applications that use GraphQL WebSocket transport with cookie-based session authentication and lack custom Spring Security WebSocket-level Origin enforcement.
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.