Spring Security: Direct Request
CVE-2026-22732 is a critical-severity direct request vulnerability in Spring Security from VMware, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Spring Security versions: 5.7.0 through 5.7.21; 5.8.0 through 5.8.23; 6.3.0 through 6.3.14, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.53% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of Spring Security you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on spring.io for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| VMware | Spring Security | 5.7.0 through 5.7.21; 5.8.0 through 5.8.23; 6.3.0 through 6.3.14; 6.4.0 through 6.4.14; 6.5.0 through 6.5.8; 7.0.0 through 7.0.3 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by CNA (vmware.com).
Official description
When applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written. This issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers: : from 5.7.0 through 5.7.21, from 5.8.0 through 5.8.23, from 6.3.0 through 6.3.14, from 6.4.0 through 6.4.14, from 6.5.0 through 6.5.8, from 7.0.0 through 7.0.3.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Direct Request
The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.
How developers prevent this class of flaw
- Apply appropriate access control authorizations for each access to all restricted URLs, scripts or files.
- Consider using MVC based frameworks such as Struts.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Spring Security
- 8.8 High severity
- 7.5 High severity
- 7.4 High severity
- 9.8 Critical severity
Recent Direct Request vulnerabilities
- 9.8 Critical severity
- 8.6 High severity
- 7.5 High severity
- 7.5 High severity
- 7.1 High severity
- 9.1 Critical severity
Spotted an error? Tell us.