CVE-2026-19323
Received Received - Intake

Path Traversal in Azer React-Analyzer-MCP

Publication date: 2026-08-09

Last updated on: 2026-08-09

Assigner: VulDB

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-09
Last Modified
2026-08-09
Generated
2026-08-09
AI Q&A
2026-08-09
EPSS Evaluated
N/A
NVD
CVE-2026-19323
EUVD
EUVD-2026-54837

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
azer react-analyzer-mcp 0.1.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a path traversal flaw in the azer react-analyzer-mcp tool up to version 335f2a3585f265e2e88352b59b10d3b478d678b0. The issue occurs in the generateProjectDocs function of src/index.ts when handling the projectName argument. By manipulating this parameter, an attacker can escape the intended project directory and access arbitrary files on the local system using path traversal sequences like ../.

Detection Guidance

Check if azer react-analyzer-mcp is installed locally by running commands like 'npm list -g azer react-analyzer-mcp' or 'which react-analyzer-mcp'. Inspect the version in src/index.ts for the vulnerable function generateProjectDocs. Look for unusual file access patterns or attempts to read files outside project directories.

Impact Analysis

An attacker with local access could read sensitive React source files (.jsx or .tsx) outside the intended project directory. This could expose proprietary code, API keys, or other confidential information stored in files. The impact is limited to local access and requires the attacker to have some level of system access already.

Compliance Impact

This vulnerability could potentially violate compliance requirements by exposing sensitive data (like personal information in React files) to unauthorized local users. GDPR requires protecting personal data, and HIPAA requires safeguarding protected health information. Unauthorized file access could lead to data breaches and non-compliance penalties.

Mitigation Strategies

Uninstall azer react-analyzer-mcp immediately using 'npm uninstall -g azer react-analyzer-mcp'. If uninstallation is not possible, restrict local access to the tool and avoid using it until a patched version is released. Monitor file system access logs for suspicious activity.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-19323. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart