Spring For GraphqlFramework / library · VMware
CVE-2026-41700
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSpring for GraphQL applications that have enabled the WebSocket transport are vulnerable to Cross-Site WebSocket Hijacking. An attacker can trick an authenticated user into visiting a malicious page, allowing the attacker to execute arbitrary GraphQL operations with the victim's credentials. 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSpring for GraphQL applications with WebSocket transport enabled lack proper Origin header validation during WebSocket handshake, allowing Cross-Site WebSocket Hijacking (CSWSH). Attackers can trick authenticated users into visiting malicious pages that establish WebSocket connections to the vulnerable GraphQL endpoint, enabling arbitrary GraphQL operations with the victim's session credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Spring For GraphqlFramework / library
>= 1.0.0, < 1.0.7>= 1.3.0, < 1.3.9>= 1.4.0, < 1.4.5.1>= 2.0.0, < 2.0.3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Spring GraphQL versionInspect your project's dependency management file (pom.xml, build.gradle, or similar) for the spring-graphql dependency and note its version. Also check the spring-graphql.jar manifest if running a built application.Affected if The installed version falls outside these safe ranges: 1.0.7+, 1.3.9+, 1.4.6+, 2.0.4+ (or you cannot determine the version)
-
Confirm WebSocket transport is enabledSearch your configuration files (application.properties, application.yml) for 'spring.graphql.graphiql.websocket.enabled' or custom GraphQL WebSocket endpoint configuration. Also check for @MessageMapping or GraphQLWsTransportRegistration in your Java/Kotlin configuration classes.Affected if WebSocket transport for GraphQL is explicitly enabled (set to true) or custom WebSocket endpoints are configured for GraphQL
-
Inspect WebSocket upgrade configurationReview your WebSocket configuration classes (annotated with @EnableWebSocket or extending WebSocketConfigurer) to see how WebSocket upgrade requests are handled. Specifically look for any Origin header validation logic.Affected if There is NO validation of the Origin header on WebSocket upgrade requests, or you cannot locate any such validation logic
-
Check GraphQL WebSocket registry settingsExamine your GraphQL WebSocket registry or interceptor configuration for allowedOrigins or origin validation settings. Look for Spring's OriginHandshakeInterceptor or custom handshake handlers.Affected if The WebSocket configuration lacks explicit Origin allowlisting or validation, or the configuration permits any Origin
Your environment is affected if you are running a vulnerable Spring for GraphQL version AND WebSocket transport is enabled AND there is no Origin header validation on WebSocket upgrade requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.0.71.3.91.4.5.1
Disable WebSocket transport in Spring GraphQL if not required, or implement strict Origin header validation and CSRF token verification for WebSocket handshake requests.
Upgrade to Spring for GraphQL 2.0.3.1, 1.4.5.1, 1.3.9, or 1.0.7 depending on your current branch
- 1. Identify the currently running version of Spring for GraphQL in your application (check pom.xml, build.gradle, or dependency management)
- 2. Determine which version branch you are on (1.0.x, 1.3.x, 1.4.x, or 2.0.x)
- 3. For Spring Boot projects: update the spring-boot-starter-graphql version in your build file to the corresponding fixed version (2.0.3.1 for 2.0.x, 1.4.5.1 for 1.4.x, 1.3.9 for 1.3.x, or 1.0.7 for 1.0.x)
- 4. Alternatively, update the spring-graphql version directly if using a standalone setup
- 5. Rebuild and test your application to ensure the upgrade does not break existing functionality
- 6. Deploy the updated application
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring For Graphql
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41700 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41700 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data