CVE-2026-41856 | Spring GraphQL Annotation Detection Vulnerability

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.

Published: 2026-06-11 Last update: 2026-06-12 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-41856 is rated Moderate Risk (41.2/100): CVSS High severity, with low exploitation likelihood (EPSS 0.39%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-41856

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.03% 0.39% +0.36%
2 2026-06-11 — 0.03% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-41856

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2026-41856

GitHub Security Advisory for CVE-2026-41856

GHSA-phxq-526m-79px · Severity: high — The Spring GraphQL annotation detection mechanism for @Controller data fetchers may not correctly...

Affected software / configurations for CVE-2026-41856

Vendor Product Version Raw CPE
vmware spring_for_graphql >= 1.0.0, < 1.0.7 cpe:2.3:a:vmware:spring_for_graphql:*:*:*:*:*:*:*:*
vmware spring_for_graphql >= 1.3.0, < 1.3.9 cpe:2.3:a:vmware:spring_for_graphql:*:*:*:*:*:*:*:*
vmware spring_for_graphql >= 1.4.0, < 1.4.6 cpe:2.3:a:vmware:spring_for_graphql:*:*:*:*:*:*:*:*
vmware spring_for_graphql >= 2.0.0, < 2.0.4 cpe:2.3:a:vmware:spring_for_graphql:*:*:*:*:*:*:*:*

References for CVE-2026-41856

cvelogic Threat Intelligence