CVE-2026-41856 is a high-severity (CVSS 7.5) CWE-284 vulnerability in org.springframework.graphql:spring-graphql. A fix is available for org.springframework.graphql:spring-graphql — see the affected versions and patch details below.
Spring GraphQL Annotation Detection Vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41856.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-41856 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 382,795 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework.graphql:spring-graphql☕org.springframework.graphql:spring-graphql☕org.springframework.graphql:spring-graphql☕org.springframework.graphql:spring-graphqlReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
The Spring GraphQL annotation detection mechanism for @Controller data fetchers may not correctly resolve annotations on methods within type hierarchies. This can be an issue if such annotations are used for authorization decisions. When all conditions are met, security annotations can be ignored at runtime.
Affected versions: Spring for GraphQL 2.0.0 through 2.0.3; 1.4.0 through 1.4.5; 1.3.0 through 1.3.8; 1.0.0 through 1.0.6.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.graphql:spring-graphql | ≥ 2.0.0&&< 2.0.4 | 2.0.4org.springframework.graphql:spring-graphql:2.0.4 |
| ☕Maven | org.springframework.graphql:spring-graphql | ≥ 1.4.0&&< 1.4.6 | 1.4.6org.springframework.graphql:spring-graphql:1.4.6 |
| ☕Maven | org.springframework.graphql:spring-graphql | ≥ 1.3.0 | No fix |
| ☕Maven | org.springframework.graphql:spring-graphql | ≥ 1.0.0 | No fix |
Affected Products
spring for graphqlvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.graphql:spring-graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.graphql:spring-graphql to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41856 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2026-41856 in your dependencies?
Find it across Maven, including transitive dependencies.