Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-41856: The Spring GraphQL annotation detection mechanism for @Controller data fetchers may not correctly resolve anno

38
Routine
HIGH 7.5REMOTEUPGRADE

CVE-2026-41856 is a high-severity flaw (CVSS 7.5) affecting spring for graphql. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.4% (top 71%)
CISA exploited listNo
WeaknessCWE-284
Published2026-06-11
Last modified2026-07-23
Publisher (CNA): VMware · Vendor: vmware

Share: LinkedIn · X · Reddit

Last updated 2026-07-23 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vmware spring for graphql UPGRADE
Affected: >= 1.0.0 and < 1.0.7 · >= 1.3.0 and < 1.3.9 · >= 1.4.0 and < 1.4.5.1 · >= 2.0.0 and < 2.0.3.1
Fixed in: 1.0.7, 1.3.9, 1.4.5.1, 2.0.3.1
Safe to downgrade to: a release before 1.0.0
1. Check installed version
apt-cache policy spring-for-graphql || rpm -q spring-for-graphql || spring-for-graphql --version
2. UPGRADE to 1.0.7 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade spring-for-graphql
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade spring-for-graphql
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.0.0 (Debian / Ubuntu)
apt-cache madison spring-for-graphql sudo apt install spring-for-graphql=<VERSION_BEFORE_1.0.0> sudo apt-mark hold spring-for-graphql
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list spring-for-graphql sudo dnf downgrade spring-for-graphql-<VERSION_BEFORE_1.0.0> sudo dnf versionlock add spring-for-graphql
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41856?

spring for graphql: upgrade to 1.0.7, 1.3.9, 1.4.5.1, 2.0.3.1. Exact commands for each OS are on this page.

Is CVE-2026-41856 being exploited?

CVE-2026-41856 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41856 affect?

CVE-2026-41856 affects spring for graphql. Severity is high (CVSS 7.5). 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 al

How urgent is CVE-2026-41856?

Priority 38/100. High severity; Remotely exploitable, no login, no user action

Software pages

VMware vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.