NocteDefensor LudusMCP up to 1.0.24 ludus_environment_guides_search ludusEnvironmentGuidesSearch.ts guide_name path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 1.82 |
Summary
A vulnerability identified as critical has been detected in NocteDefensor LudusMCP up to 1.0.24. This affects an unknown function of the file src/tools/ludusEnvironmentGuidesSearch.ts of the component ludus_environment_guides_search. Performing a manipulation of the argument guide_name results in path traversal. This vulnerability was named CVE-2026-19046. The attack needs to be approached locally. There is no available exploit. The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability was found in NocteDefensor LudusMCP up to 1.0.24. It has been classified as problematic. This affects some unknown functionality of the file src/tools/ludusEnvironmentGuidesSearch.ts of the component ludus_environment_guides_search. The manipulation of the argument guide_name 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-19046. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
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
Vendor
Name
Version
- 1.0.0
- 1.0.1
- 1.0.2
- 1.0.3
- 1.0.4
- 1.0.5
- 1.0.6
- 1.0.7
- 1.0.8
- 1.0.9
- 1.0.10
- 1.0.11
- 1.0.12
- 1.0.13
- 1.0.14
- 1.0.15
- 1.0.16
- 1.0.17
- 1.0.18
- 1.0.19
- 1.0.20
- 1.0.21
- 1.0.22
- 1.0.23
- 1.0.24
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
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: 🔒
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
08/06/2026 Advisory disclosed08/06/2026 VulDB entry created
08/06/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Not defined
Confirmation: 🔒
CVE: CVE-2026-19046 (🔒)
GCVE (CVE): GCVE-0-2026-19046
GCVE (VulDB): GCVE-100-386493
Entry
Created: 08/06/2026 09:39Changes: 08/06/2026 09:39 (56)
Complete: 🔍
Submitter: gongyanyu
Cache ID: 216::103
Submit
Accepted
- Submit #863834: NocteDefensor LudusMCP unknown Path Traversal (by gongyanyu)
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.