Sensiolabs Symfony up to 5.4.53/6.4.47/7.4.20/8.1.8 ExpressionLanguage ExpressionLanguage::lint resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Sensiolabs Symfony up to 5.4.53/6.4.47/7.4.20/8.1.8 and classified as problematic. The affected element is the function ExpressionLanguage::lint of the component ExpressionLanguage. The manipulation results in resource consumption.
This vulnerability is known as CVE-2026-109449. It is possible to launch the attack remotely. No exploit is available.
It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Sensiolabs Symfony up to 5.4.53/6.4.47/7.4.20/8.1.8. Affected is the function ExpressionLanguage::lint of the component ExpressionLanguage. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. CVE summarizes:
In Symfony Expression Language versions prior to 5.4.54, 6.4.48, 7.4.21, and 8.1.9, the parser of the ExpressionLanguage component built its node tree with no bound on its depth. An expression made of tens of thousands of nested unary operators, array literals, binary operators or property accesses crashed the PHP process, while the tree was being freed. #[Assert\ExpressionSyntax] passes the validated value to ExpressionLanguage::lint(), so an application validating expressions written by its users could be crashed by a single request, and so could any code parsing untrusted expressions. This issue affects symfony/expression-language through v5.4.53, v6.0.0-BETA1 through v6.4.47, v7.0.0-BETA1 through v7.4.20, and v8.0.0-BETA1 through v8.1.8.
The advisory is available at github.com. This vulnerability is traded as CVE-2026-109449 since 10/12/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. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.
Upgrading to version 5.4.54, 6.4.48, 7.4.21 or 8.1.9 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 5.4.0
- 5.4.1
- 5.4.2
- 5.4.3
- 5.4.4
- 5.4.5
- 5.4.6
- 5.4.7
- 5.4.8
- 5.4.9
- 5.4.10
- 5.4.11
- 5.4.12
- 5.4.13
- 5.4.14
- 5.4.15
- 5.4.16
- 5.4.17
- 5.4.18
- 5.4.19
- 5.4.20
- 5.4.21
- 5.4.22
- 5.4.23
- 5.4.24
- 5.4.25
- 5.4.26
- 5.4.27
- 5.4.28
- 5.4.29
- 5.4.30
- 5.4.31
- 5.4.32
- 5.4.33
- 5.4.34
- 5.4.35
- 5.4.36
- 5.4.37
- 5.4.38
- 5.4.39
- 5.4.40
- 5.4.41
- 5.4.42
- 5.4.43
- 5.4.44
- 5.4.45
- 5.4.46
- 5.4.47
- 5.4.48
- 5.4.49
- 5.4.50
- 5.4.51
- 5.4.52
- 5.4.53
- 6.4.0
- 6.4.1
- 6.4.2
- 6.4.3
- 6.4.4
- 6.4.5
- 6.4.6
- 6.4.7
- 6.4.8
- 6.4.9
- 6.4.10
- 6.4.11
- 6.4.12
- 6.4.13
- 6.4.14
- 6.4.15
- 6.4.16
- 6.4.17
- 6.4.18
- 6.4.19
- 6.4.20
- 6.4.21
- 6.4.22
- 6.4.23
- 6.4.24
- 6.4.25
- 6.4.26
- 6.4.27
- 6.4.28
- 6.4.29
- 6.4.30
- 6.4.31
- 6.4.32
- 6.4.33
- 6.4.34
- 6.4.35
- 6.4.36
- 6.4.37
- 6.4.38
- 6.4.39
- 6.4.40
- 6.4.41
- 6.4.42
- 6.4.43
- 6.4.44
- 6.4.45
- 6.4.46
- 6.4.47
- 7.4.0
- 7.4.1
- 7.4.2
- 7.4.3
- 7.4.4
- 7.4.5
- 7.4.6
- 7.4.7
- 7.4.8
- 7.4.9
- 7.4.10
- 7.4.11
- 7.4.12
- 7.4.13
- 7.4.14
- 7.4.15
- 7.4.16
- 7.4.17
- 7.4.18
- 7.4.19
- 7.4.20
- 8.1.0
- 8.1.1
- 8.1.2
- 8.1.3
- 8.1.4
- 8.1.5
- 8.1.6
- 8.1.7
- 8.1.8
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Resource consumptionCWE: CWE-400 / 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: Symfony 5.4.54/6.4.48/7.4.21/8.1.9
Timeline
10/12/2026 CVE reserved10/15/2026 Advisory disclosed
10/15/2026 VulDB entry created
10/15/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-109449 (🔒)
GCVE (CVE): GCVE-0-2026-109449
GCVE (VulDB): GCVE-100-420690
Entry
Created: 10/15/2026 17:50Changes: 10/15/2026 17:50 (69)
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.