Spring Framework No Origin Validation If WebSocket Handling Configured Directly

MEDIUM | NOVEMBER 19, 2026 | CVE-2026-59390

Description

Spring Framework's WebSocket support does not validate the Origin header by default if WebSocketHttpRequestHandler is configured directly by the application, rather than through the WebSocket config via WebSocketHandlerRegistry.

An application is affected if it configures WebSocket handling this way without adding an origin check. In that case, a page served from a different origin can open a WebSocket connection resulting in cross-site WebSocket hijacking. Applications that use the WebSocket config via WebSocketHandlerRegistry are not affected.

Affected Spring Products and Versions

Spring Framework:

  • 7.0.0 - 7.0.10
  • 6.2.0 - 6.2.20
  • 6.1.0 - 6.1.29
  • 6.0.0 - 6.0.32
  • 5.3.0 - 5.3.50
  • 5.2.26.RELEASE and earlier

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.
Fix versionAvailability
7.0.11OSS
7.0.10.1Enterprise Support Only
6.2.21Enterprise Support Only
6.1.30Enterprise Support Only
6.0.33Enterprise Support Only
5.3.51Enterprise Support Only
5.2.27.RELEASEEnterprise Support Only

No further mitigation steps are necessary.

Credit

This issue was discovered by Xint, reported via Project Canopy.

History

  • 2026-11-19: Initial vulnerability report published.

Get ahead

VMware offers training and certification to turbo-charge your progress.

Learn more

Get support

TrueSource Spring Enterprise offers support and binaries for OpenJDK™, Spring, and Apache Tomcat® in one simple subscription.

Learn more

Upcoming events

Check out all the upcoming events in the Spring community.

View all