CVE Watchtower

CVE-2026-59391Spring Framework

Spring

Vulnerability Summary

Spring Framework Message Smuggling with External STOMP Broker. Spring Framework's STOMP broker relay can allow an authenticated user to bypass message authorization rules when an external STOMP broker is used. An application is affected if it uses the STOMP broker relay with an external broker and relies on Spring Security message authorization to restrict access to destinations. In that case, a specially crafted sequence of STOMP frames can cause the broker to process commands that the application's authorization rules would otherwise deny, potentially allowing a user to send or receive messages on restricted destinations.
Severity Level
MEDIUM(5.9)
Published Date
Nov 19, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Reserved
This CVE ID is referenced in a public advisory, but the CVE Program has not published its official CVE Record yet. Full CVSS/CPE data from NVD will appear here once it does.
Root Weakness (CWE)
See the MITRE CWE entry for the full definition of this weakness.
CVSS v3.1 Base Metrics — Score 5.9 (MEDIUM)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredLow
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityLow
AvailabilityNone

Affected & Patched Versions

Affected Versions
  • Spring Framework 7.0.0 through 7.0.10
  • Spring Framework 6.2.0 through 6.2.20
  • Spring Framework 6.1.0 through 6.1.29
  • Spring Framework 6.0.0 through 6.0.32
  • Spring Framework 5.3.0 through 5.3.50
  • Spring Framework through 5.2.26.RELEASE
Patched Versions
  • Spring Framework 7.0.11 (open source)
  • Spring Framework 7.0.10.1 (commercial support only)
  • Spring Framework 6.2.21 (commercial support only)
  • Spring Framework 6.1.30 (commercial support only)
  • Spring Framework 6.0.33 (commercial support only)
  • Spring Framework 5.3.51 (commercial support only)
  • Spring Framework 5.2.27.RELEASE (commercial support only)

What to do

Fix it during your normal patch cycle. No exploitation is confirmed yet.

  1. Check whether you run Spring Framework and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Nov 19, 2026Published
  • Nov 19, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Spring Framework CVEsYou are reading CVE-2026-59391. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More Spring Framework CVEs

External References

Data last checked: Nov 20, 2026 05:01 UTC