VMware Spring Cloud Function up to 3.2.16/4.2.7/4.3.4/5.0.3 modification of assumed-immutable data
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $5k-$25k | 0.64 |
Summary
A vulnerability, which was classified as problematic, was found in VMware Spring Cloud Function up to 3.2.16/4.2.7/4.3.4/5.0.3. The impacted element is an unknown function. Executing a manipulation can lead to modification of assumed-immutable data. This vulnerability is registered as CVE-2026-59299. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability classified as problematic was found in VMware Spring Cloud Function up to 3.2.16/4.2.7/4.3.4/5.0.3. This vulnerability affects some unknown functionality. The manipulation with an unknown input leads to a modification of assumed-immutable data vulnerability. The CWE definition for the vulnerability is CWE-471. The product does not properly protect an assumed-immutable element from being modified by an attacker. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Composition lookup can potentially poison base function in Spring Cloud Function. Spring Cloud Function 5.0.0 - 5.0.3 Spring Cloud Function 4.3.0 - 4.3.4 Spring Cloud Function 4.2.0 - 4.2.7 Spring Cloud Function 3.2.16 and earlier
The advisory is available at spring.io. This vulnerability was named CVE-2026-59299 since 07/04/2026. The exploitation appears to be easy. The attack can be initiated remotely. The exploitation requires an enhanced level of successful authentication. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 08/27/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 3.2.0
- 3.2.1
- 3.2.2
- 3.2.3
- 3.2.4
- 3.2.5
- 3.2.6
- 3.2.7
- 3.2.8
- 3.2.9
- 3.2.10
- 3.2.11
- 3.2.12
- 3.2.13
- 3.2.14
- 3.2.15
- 3.2.16
- 4.2.0
- 4.2.1
- 4.2.2
- 4.2.3
- 4.2.4
- 4.2.5
- 4.2.6
- 4.2.7
- 4.3.0
- 4.3.1
- 4.3.2
- 4.3.3
- 4.3.4
- 5.0.0
- 5.0.1
- 5.0.2
- 5.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: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.1
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: Modification of assumed-immutable dataCWE: CWE-471
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/04/2026 CVE reserved08/27/2026 Advisory disclosed
08/27/2026 VulDB entry created
08/27/2026 VulDB entry last update
Sources
Vendor: vmware.comAdvisory: spring.io
Status: Not defined
CVE: CVE-2026-59299 (🔒)
GCVE (CVE): GCVE-0-2026-59299
GCVE (VulDB): GCVE-100-396370
scip Labs: https://www.scip.ch/en/?labs.20060413
Entry
Created: 08/27/2026 22:55Changes: 08/27/2026 22:55 (61)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.