What is CVE-2026-15751?
A security vulnerability has been detected in mastergo-design mastergo-magic-mcp up to 0.2.0. The affected element is the function execute of the file mastergo/component-workflow.md of the component mcp__getComponentGenerator. The manipulation of the argument rootPath leads to path traversal. An attack has to be approached locally. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.
The record classifies CVE-2026-15751 under weakness class CWE-22. Its CVSS v3 base vector states that the flaw requires local access to the host, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 83 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 5.3 — MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R - CVSS v4.0 base score
- 4.8
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 - EPSS (FIRST)
- 0.1% probability of exploitation in the next 30 days, higher than 3.7% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 2.8/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-07-14, last modified 2026-07-15
Is CVE-2026-15751 being exploited?
It currently carries a trending score of 31 in the Threadlinqs vulnerability feed.
Affected products and versions
- mastergo-design: mastergo-magic-mcp
How to fix CVE-2026-15751
No vendor patch reference has been recorded for CVE-2026-15751 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-15751
No threat campaign in the Threadlinqs corpus currently references CVE-2026-15751, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on .