alioshr memory-bank-mcp up to 0.2.1/3.1 list-project-files-validation-factory.ts projectName path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 2.17 |
Summary
A vulnerability was found in alioshr memory-bank-mcp up to 0.2.1/3.1. It has been rated as problematic. This vulnerability affects unknown code of the file list-project-files-validation-factory.ts. Performing a manipulation of the argument projectName results in path traversal. This vulnerability was named CVE-2026-15524. The attack needs to be approached locally. In addition, an exploit is available. The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability was found in alioshr memory-bank-mcp up to 0.2.1/3.1. It has been classified as problematic. This affects an unknown function of the file list-project-files-validation-factory.ts. The manipulation of the argument projectName with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on confidentiality.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-15524. The exploitability is told to be easy. An attack has to be approached locally. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1006 for this issue.
The exploit is shared for download 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: Path traversalCWE: CWE-22
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
07/12/2026 Advisory disclosed07/12/2026 VulDB entry created
07/12/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 36
Status: Not defined
CVE: CVE-2026-15524 (🔒)
GCVE (CVE): GCVE-0-2026-15524
GCVE (VulDB): GCVE-100-377853
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/12/2026 14:09Changes: 07/12/2026 14:09 (58)
Complete: 🔍
Submitter: Mcfly_Zhang
Cache ID: 216::103
Submit
Accepted
- Submit #854526: alioshr memory-bank-mcp 0.2.1 Directory Enumeration (by Mcfly_Zhang)
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.