Local React source disclosure via unchecked project path
Published Aug 9, 2026 · Updated Aug 9, 2026
Path traversal in Azer Koçulu react-analyzer-mcp 0.1.0 allows local users to read React source files via crafted project names. The analyze-project handler passes projectName to path.join without a containment check, recursively scans the resulting directory, and reads discovered .jsx and .tsx files. Access to a local MCP client is required, and disclosure is limited to React source files readable by the server process outside PROJECT_ROOT.
Summary
What happened
Path traversal in Azer Koçulu react-analyzer-mcp 0.1.0 allows local users to read React source files via crafted project names. The analyze-project handler passes projectName to path.join without a containment check, recursively scans the resulting directory, and reads discovered .jsx and .tsx files. Access to a local MCP client is required, and disclosure is limited to React source files readable by the server process outside PROJECT_ROOT.
The record
- CVE
- CVE-2026-19323
- Published
- Aug 9, 2026
- Updated
- Aug 9, 2026
- Vendor
- Azer Koçulu
- Product
- react-analyzer-mcp
- Classifications
- CWE-22, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 9, 2026CVE publishedPublication date reported by the CVE source.
- Aug 9, 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=335f2a3585f265e2e88352b59b10d3b478d678b0
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