Local file disclosure via unvalidated C2d path
Published Jul 14, 2026 · Updated Jul 14, 2026
Path traversal in MasterGo Magic MCP 0.1 through 0.2.0 allows local users to read process-accessible files via mcp__C2d. The execute function passes the caller-controlled filePath directly to fs.readFileSync without canonicalization or a directory-boundary check, then posts the file body to MasterGo's postC2d endpoint. An MCP client or prompt-injected agent must be able to invoke the local stdio tool; disclosure is limited to files readable by the service account.
Summary
What happened
Path traversal in MasterGo Magic MCP 0.1 through 0.2.0 allows local users to read process-accessible files via mcp__C2d. The execute function passes the caller-controlled filePath directly to fs.readFileSync without canonicalization or a directory-boundary check, then posts the file body to MasterGo's postC2d endpoint. An MCP client or prompt-injected agent must be able to invoke the local stdio tool; disclosure is limited to files readable by the service account.
The record
- CVE
- CVE-2026-15749
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- MasterGo
- Product
- MasterGo Magic MCP
- Classifications
- CWE-22, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.1
- Affected versionversion=0.2.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue 88 local file-read reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo