Vmware Spring Framework up to 5.3.48/6.1.27/6.2.18/7.0.7 Spring Expression Language algorithmic complexity
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Vmware Spring Framework up to 5.3.48/6.1.27/6.2.18/7.0.7. It has been declared as problematic. Impacted is an unknown function of the component Spring Expression Language Handler. The manipulation results in algorithmic complexity. This vulnerability is identified as CVE-2026-41850. The attack can be executed remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in Vmware Spring Framework up to 5.3.48/6.1.27/6.2.18/7.0.7. Affected is some unknown processing of the component Spring Expression Language Handler. The manipulation with an unknown input leads to a algorithmic complexity vulnerability. CWE is classifying the issue as CWE-407. An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached. This is going to have an impact on availability. CVE summarizes:
Applications that evaluate user-supplied Spring Expression Language (SpEL) expressions are vulnerable to an Algorithmic Denial of Service (DoS). By providing a specially crafted expression, an attacker can trigger excessive resource consumption during evaluation, leading to application degradation or unavailability. Affected versions: Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48.
The advisory is shared for download at spring.io. This vulnerability is traded as CVE-2026-41850 since 04/22/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 06/09/2026). The MITRE ATT&CK project declares the attack technique as T1499.
Upgrading to version 5.3.49, 6.1.28, 6.2.18.1, 6.2.19, 7.0.7.1 or 7.0.8 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 5.3.0
- 5.3.1
- 5.3.2
- 5.3.3
- 5.3.4
- 5.3.5
- 5.3.6
- 5.3.7
- 5.3.8
- 5.3.9
- 5.3.10
- 5.3.11
- 5.3.12
- 5.3.13
- 5.3.14
- 5.3.15
- 5.3.16
- 5.3.17
- 5.3.18
- 5.3.19
- 5.3.20
- 5.3.21
- 5.3.22
- 5.3.23
- 5.3.24
- 5.3.25
- 5.3.26
- 5.3.27
- 5.3.28
- 5.3.29
- 5.3.30
- 5.3.31
- 5.3.32
- 5.3.33
- 5.3.34
- 5.3.35
- 5.3.36
- 5.3.37
- 5.3.38
- 5.3.39
- 5.3.40
- 5.3.41
- 5.3.42
- 5.3.43
- 5.3.44
- 5.3.45
- 5.3.46
- 5.3.47
- 5.3.48
- 6.1.0
- 6.1.1
- 6.1.2
- 6.1.3
- 6.1.4
- 6.1.5
- 6.1.6
- 6.1.7
- 6.1.8
- 6.1.9
- 6.1.10
- 6.1.11
- 6.1.12
- 6.1.13
- 6.1.14
- 6.1.15
- 6.1.16
- 6.1.17
- 6.1.18
- 6.1.19
- 6.1.20
- 6.1.21
- 6.1.22
- 6.1.23
- 6.1.24
- 6.1.25
- 6.1.26
- 6.1.27
- 6.2.0
- 6.2.1
- 6.2.2
- 6.2.3
- 6.2.4
- 6.2.5
- 6.2.6
- 6.2.7
- 6.2.8
- 6.2.9
- 6.2.10
- 6.2.11
- 6.2.12
- 6.2.13
- 6.2.14
- 6.2.15
- 6.2.16
- 6.2.17
- 6.2.18
- 7.0.0
- 7.0.1
- 7.0.2
- 7.0.3
- 7.0.4
- 7.0.5
- 7.0.6
- 7.0.7
License
Website
- Vendor: https://www.vmware.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
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: Algorithmic complexityCWE: CWE-407 / CWE-404
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 Framework 5.3.49/6.1.28/6.2.18.1/6.2.19/7.0.7.1/7.0.8
Timeline
04/22/2026 CVE reserved06/09/2026 Advisory disclosed
06/09/2026 VulDB entry created
06/09/2026 VulDB entry last update
Sources
Vendor: vmware.comAdvisory: spring.io
Status: Confirmed
CVE: CVE-2026-41850 (🔒)
GCVE (CVE): GCVE-0-2026-41850
GCVE (VulDB): GCVE-100-369396
scip Labs: https://www.scip.ch/en/?labs.20060413
Entry
Created: 06/09/2026 07:33Changes: 06/09/2026 07:33 (64)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.