EUVD-2026-54837
GHSA-g23h-49jw-gw6q
Severity by source
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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Local-only attack vector and low-privilege requirement per description; limited low-severity read/write impact within the vulnerable system only, no scope change.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A security flaw has been discovered in azer react-analyzer-mcp up to 335f2a3585f265e2e88352b59b10d3b478d678b0. Affected by this vulnerability is the function generateProjectDocs of the file src/index.ts of the component analyze-projec. The manipulation of the argument projectName results in path traversal. The attack is only possible with local access. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The project was informed of the problem early through an issue report but has not responded yet.
AnalysisAI
Path traversal in azer's react-analyzer-mcp MCP server allows local low-privilege attackers to read or write files outside the intended project directory by supplying crafted input to the projectName argument of the generateProjectDocs function in src/index.ts. All commits up to 335f2a3585f265e2e88352b59b10d3b478d678b0 are affected, with no vendor-released patch available as the maintainer has not yet responded to the disclosure via GitHub issue. No public exploit identified at time of analysis, though the CVSS 4.0 E:P modifier indicates a proof-of-concept exists, and the attack is constrained to local authenticated access only.
Technical ContextAI
react-analyzer-mcp is a TypeScript-based Model Context Protocol (MCP) server designed to analyze React project structures and generate project documentation. The vulnerable component is analyze-project, specifically the generateProjectDocs function in src/index.ts, which constructs filesystem paths using the caller-supplied projectName argument. CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) identifies the root cause: the function does not normalize or validate the input before using it to construct a file path, allowing traversal sequences such as ../../ to escape the intended project root. CPE cpe:2.3:a:azer:react-analyzer-mcp:*:*:*:*:*:*:*:* covers all releases of this product. As an MCP server, it is typically invoked programmatically by AI toolchains or developer environments, meaning the attack surface is local developer workstations or CI systems running the tool.
RemediationAI
No vendor-released patch is available at time of analysis. The project maintainer was notified via GitHub issue #3 (https://github.com/azer/react-analyzer-mcp/issues/3) but has not responded. The most actionable compensating control is to restrict access to any system running react-analyzer-mcp to trusted users only, since exploitation requires local authenticated access - this eliminates the threat from untrusted local users without requiring code changes. Developers who require a fix immediately may fork the repository and apply input validation on the projectName parameter in generateProjectDocs using Node.js path.resolve() combined with a check that the resolved path begins with the expected project root, rejecting any path that escapes it. Monitor https://github.com/azer/react-analyzer-mcp/ for upstream commits addressing the issue. Avoid exposing the MCP server's tooling interface to shared or multi-tenant environments until the fix lands.
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today