Authorization bypass in Spring for GraphQL annotation detection
CVE-2026-41856 is a high-severity vulnerability in Spring for GraphQL affecting the annotation detection mechanism used for @Controller data fetchers. In affected versions, annotations on methods within type hierarchies may not be resolved correctly at runtime. If security annotations are relied upon for authorization decisions, this resolution failure can cause those annotations to be ignored. The issue is specifically relevant where authorization is enforced through Spring Security method-security annotations on controller methods participating in inheritance or other type-hierarchy relationships.
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 annotation detection flaw in Spring GraphQL that can bypass or ignore runtime security checks within complex type hierarchies.
An authorization bypass vulnerability in Spring for GraphQL where annotation detection for @Controller data fetchers in type hierarchies can fail, causing Spring Security method security annotations to be ignored at runtime under specific conditions.
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.