VMware Spring Security up to 4.0.3 CloudFoundry Actuator Endpoint authentication bypass
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in VMware Spring Security up to 2.7.31/3.3.17/3.4.14/3.5.11/4.0.3 and classified as critical. The impacted element is an unknown function of the component CloudFoundry Actuator Endpoint. Performing a manipulation results in authentication bypass. This vulnerability was named CVE-2026-22733. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability classified as critical has been found in VMware Spring Security up to 2.7.31/3.3.17/3.4.14/3.5.11/4.0.3. This affects an unknown part of the component CloudFoundry Actuator Endpoint. The manipulation with an unknown input leads to a authentication bypass vulnerability. CWE is classifying the issue as CWE-288. A product requires authentication, but the product has an alternate path or channel that does not require authentication. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Spring Boot applications with Actuator can be vulnerable to an "Authentication Bypass" vulnerability when an application endpoint that requires authentication is declared under the path used by the CloudFoundry Actuator endpoints. This issue affects Spring Security: from 4.0.0 through 4.0.3, from 3.5.0 through 3.5.11, from 3.4.0 through 3.4.14, from 3.3.0 through 3.3.17, from 2.7.0 through 2.7.31.
It is possible to read the advisory at spring.io. This vulnerability is uniquely identified as CVE-2026-22733 since 01/09/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/15/2026).
Upgrading to version 2.7.32, 3.3.18, 3.4.15, 3.5.12 or 4.0.4 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0799). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- Red Hat Enterprise Linux
- VMware Tanzu Spring Boot
Product
Vendor
Name
Version
- 2.7.0
- 2.7.1
- 2.7.2
- 2.7.3
- 2.7.4
- 2.7.5
- 2.7.6
- 2.7.7
- 2.7.8
- 2.7.9
- 2.7.10
- 2.7.11
- 2.7.12
- 2.7.13
- 2.7.14
- 2.7.15
- 2.7.16
- 2.7.17
- 2.7.18
- 2.7.19
- 2.7.20
- 2.7.21
- 2.7.22
- 2.7.23
- 2.7.24
- 2.7.25
- 2.7.26
- 2.7.27
- 2.7.28
- 2.7.29
- 2.7.30
- 2.7.31
- 3.3.0
- 3.3.1
- 3.3.2
- 3.3.3
- 3.3.4
- 3.3.5
- 3.3.6
- 3.3.7
- 3.3.8
- 3.3.9
- 3.3.10
- 3.3.11
- 3.3.12
- 3.3.13
- 3.3.14
- 3.3.15
- 3.3.16
- 3.3.17
- 3.4.0
- 3.4.1
- 3.4.2
- 3.4.3
- 3.4.4
- 3.4.5
- 3.4.6
- 3.4.7
- 3.4.8
- 3.4.9
- 3.4.10
- 3.4.11
- 3.4.12
- 3.4.13
- 3.4.14
- 3.5.0
- 3.5.1
- 3.5.2
- 3.5.3
- 3.5.4
- 3.5.5
- 3.5.6
- 3.5.7
- 3.5.8
- 3.5.9
- 3.5.10
- 3.5.11
- 4.0.0
- 4.0.1
- 4.0.2
- 4.0.3
License
Website
- Vendor: https://www.vmware.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.7VulDB Meta Temp Score: 7.6
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.2
CNA Vector (vmware): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Authentication bypassCWE: CWE-288 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Spring Security 2.7.32/3.3.18/3.4.15/3.5.12/4.0.4
Timeline
01/09/2026 CVE reserved03/20/2026 Advisory disclosed
03/20/2026 VulDB entry created
05/15/2026 VulDB entry last update
Sources
Vendor: vmware.comAdvisory: spring.io
Status: Confirmed
CVE: CVE-2026-22733 (🔒)
GCVE (CVE): GCVE-0-2026-22733
GCVE (VulDB): GCVE-100-351963
CERT Bund: WID-SEC-2026-0799 - VMware Tanzu Spring Boot Actuator: Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen
scip Labs: https://www.scip.ch/en/?labs.20060413
Entry
Created: 03/20/2026 08:26Updated: 05/15/2026 11:01
Changes: 03/20/2026 08:26 (64), 03/20/2026 11:26 (7), 03/23/2026 00:51 (1), 05/15/2026 11:01 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.