Local JSON file manipulation via unchecked identifier
Published Aug 8, 2026 · Updated Aug 8, 2026
Path traversal in HistoryService in Alex Brinsmead Mindpilot MCP 0.5.0 allows local users to read, overwrite, or delete JSON files. HTTP history routes pass an attacker-controlled id to path.join, which appends .json without validating the identifier or checking that the result remains under the data directory. Exploitation requires access to the locally hosted HTTP service, and filesystem permissions bound which JSON files can be manipulated.
Summary
What happened
Path traversal in HistoryService in Alex Brinsmead Mindpilot MCP 0.5.0 allows local users to read, overwrite, or delete JSON files. HTTP history routes pass an attacker-controlled id to path.join, which appends .json without validating the identifier or checking that the result remains under the data directory. Exploitation requires access to the locally hosted HTTP service, and filesystem permissions bound which JSON files can be manipulated.
The record
- CVE
- CVE-2026-19287
- Published
- Aug 8, 2026
- Updated
- Aug 8, 2026
- Vendor
- Alex Brinsmead
- Product
- Mindpilot MCP
- Classifications
- CWE-22, T1005, T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 8, 2026CVE publishedPublication date reported by the CVE source.
- Aug 8, 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.5.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
No public exploit references are available in this record.
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