Skip to main content
VulnerabilityPublished Updated

CVE-2026-19270: Hulupeep mcp-ui-probe · Path Traversal

Affects Hulupeep mcp-ui-probeSource CVE Database V5

0
Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 6 Nov 2026, 23:24 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Hulupeepmcp-ui-probeAffected
  • =0.1
  • =0.2.0
Fixed in–
GitHubhulupeep/mcp-ui-probepkg:github/hulupeep/mcp-ui-probeOther threatsAffected
  • =0.1
  • =0.2.0
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:hulupeep:mcp-ui-probe:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should restrict local access to trusted users only and monitor for any suspicious activity involving the affected functions. Check the vendor advisory regularly for updates or patches addressing this vulnerability.

Description

A security flaw has been discovered in Hulupeep mcp-ui-probe up to 0.2.0. Affected 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 results in path traversal. The attack requires a local approach. The project was informed of the problem early through an issue report but has not responded yet.

References

Community reviews

Loading reviews…