CVE-2026-41856: Spring for GraphQL · Improper Access Control
Affects Spring for GraphQLSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 2.0.3.1 : patch Spring for GraphQL soon.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.3.1, 1.4.5.1, 1.3.9 +1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade Spring for GraphQL to 2.0.3.1, 1.4.5.1, 1.3.9 or 1.0.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SpringSpring for GraphQL | Affected
| Fixed in
|
| SpringSpring for GraphQL | Affected
| Fixed in
|
| SpringSpring for GraphQL | Affected
| Fixed in
|
| SpringSpring for GraphQL | Affected
| Fixed in
|
Mavenorg.springframework.graphql/spring-graphqlpkg:maven/org.springframework.graphql/spring-graphqlOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, carefully review and test authorization configurations in Spring for GraphQL applications to identify potential bypasses related to annotation detection in type hierarchies.
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.