llvm llvm-project up to 22.1.6 ValueSymbolTable ValueSymbolTable.cpp llvm::StringMap::insert stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 2.90 |
Summary
A vulnerability marked as problematic has been reported in llvm llvm-project up to 22.1.6. This impacts the function llvm::StringMap::insert in the library /lib/IR/ValueSymbolTable.cpp of the component ValueSymbolTable Module. This manipulation causes stack-based overflow.
This vulnerability is handled as CVE-2026-13573. It is possible to launch the attack on the local host. Additionally, an exploit exists.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability classified as problematic was found in llvm llvm-project up to 22.1.6. Affected by this vulnerability is the function llvm::StringMap::insert in the library /lib/IR/ValueSymbolTable.cpp of the component ValueSymbolTable Module. The manipulation with an unknown input leads to a stack-based overflow vulnerability. The CWE definition for the vulnerability is CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). As an impact it is known to affect availability.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-13573. The exploitation appears to be easy. An attack has to be approached locally. Technical details and also a public exploit are known.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.
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 the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
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: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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
06/28/2026 Advisory disclosed06/28/2026 VulDB entry created
06/28/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 199187
Status: Not defined
CVE: CVE-2026-13573 (🔒)
GCVE (CVE): GCVE-0-2026-13573
GCVE (VulDB): GCVE-100-374581
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/28/2026 20:52Changes: 06/28/2026 20:52 (59)
Complete: 🔍
Submitter: TYGLS
Cache ID: 216::103
Submit
Accepted
- Submit #844457: LLVM LLVM Project commit 3b3a3c2 Stack-based Buffer Overflow (by TYGLS)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.