Hulupeep mcp-ui-probe up to 0.2.0 Journey/Usage JourneyStorage.ts journeyId/filename path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 2.68 |
Summary
A vulnerability marked as critical has been reported in Hulupeep mcp-ui-probe up to 0.2.0. Affected by this vulnerability is the function get_journey/delete_journey/analyze_journey/usage_stats of the file src/journey/JourneyStorage.ts of the component Journey/Usage. This manipulation of the argument journeyId/filename causes path traversal.
This vulnerability appears as CVE-2026-19270. The attack requires local access. 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 has been found in Hulupeep mcp-ui-probe up to 0.2.0 and classified as critical. Affected by this vulnerability is the function get_journey/delete_journey/analyze_journey/usage_stats of the file src/journey/JourneyStorage.ts of the component Journey/Usage. The manipulation of the argument journeyId/filename with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-19270. The exploitation appears to be easy. An attack has to be approached locally. Technical details and also a exploit are known. MITRE ATT&CK project uses the attack technique T1006 for this issue.
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: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: Proof-of-Concept
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/07/2026 Advisory disclosed08/07/2026 VulDB entry created
08/07/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Not defined
CVE: CVE-2026-19270 (🔒)
GCVE (CVE): GCVE-0-2026-19270
GCVE (VulDB): GCVE-100-387013
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/07/2026 16:21Changes: 08/07/2026 16:21 (58)
Complete: 🔍
Submitter: gongyanyu02
Cache ID: 216::103
Submit
Accepted
- Submit #865223: Hulupeep mcp-ui-probe mcp-ui-probe Path Traversal (by gongyanyu02)
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.