Which versions of Mcp Docs Rag are affected by CVE-2026-5007?

Organizations using kazuph mcp-docs-rag should be aware of moderate risk from CVE-2026-5007, a OS command injection vulnerability rated CVSS 4.8.

Is there a public PoC exploit available for CVE-2026-5007?

Yes, a public proof-of-concept exploit is available for CVE-2026-5007. Prioritise patching immediately. EPSS: 0.2%.

How to fix or mitigate CVE-2026-5007?

Within 30 days: Identify affected systems running kazuph mcp-docs-rag and apply vendor patches as part of regular patch cycle. Validate input sanitization for user-controlled parameters.

Mcp Docs Rag CVE-2026-5007

Q: What is the CVSS score of CVE-2026-5007?

CVE-2026-5007 has a CVSS 4.0 base score of 1.9 (Low). CVSS vector: 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. EPSS exploitation probability: 0.2%.

EUVD-2026-16941 LOW

OS Command Injection (CWE-78)

2026-03-28 VulDB

GHSA-56ph-gvwc-wqxr

Command Injection Mcp Docs Rag

1.9

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

1.9 LOW

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Severity Changed

Apr 29, 2026 - 01:11 NVD

MEDIUM LOW

CVSS changed

Apr 29, 2026 - 01:11 NVD

4.8 (MEDIUM) 1.9 (LOW)

PoC Detected

Mar 30, 2026 - 13:26 vuln.today

Public exploit code

EUVD ID Assigned

Mar 28, 2026 - 19:00 euvd

EUVD-2026-16941

Analysis Generated

Mar 28, 2026 - 19:00 vuln.today

CVE Published

Mar 28, 2026 - 18:30 nvd

MEDIUM 4.8

DescriptionCVE.org

A vulnerability was identified in kazuph mcp-docs-rag up to 0.5.0. Affected is the function cloneRepository of the file src/index.ts of the component add_git_repository/add_text_file. The manipulation leads to os command injection. The attack needs to be performed locally. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.

AnalysisAI

OS command injection in kazuph mcp-docs-rag through version 0.5.0 allows local attackers with limited privileges to execute arbitrary commands via the cloneRepository function in src/index.ts. The vulnerability affects the add_git_repository and add_text_file components, with publicly available exploit code demonstrating the attack. No vendor patch has been released despite early notification through a GitHub issue.

Technical ContextAI

The vulnerability exists in the cloneRepository function within the mcp-docs-rag component, which handles git repository operations. The root cause is classified as CWE-78 (Improper Neutralization of Special Elements used in an OS Command), indicating that user-controlled input is passed unsanitized to OS command execution mechanisms. The affected component processes repository URLs or file paths through git commands without proper input validation or escaping, allowing injection of shell metacharacters. mcp-docs-rag is a Model Context Protocol (MCP) server implementation that manages document retrieval and RAG (Retrieval-Augmented Generation) workflows, making command injection in repository cloning a direct path to system compromise for users leveraging this tool.

RemediationAI

No vendor-released patch is currently available. Immediate remediation requires either discontinuing use of mcp-docs-rag or restricting access to the cloneRepository functionality to only trusted administrators. Organizations should monitor the official GitHub repository (https://github.com/kazuph/mcp-docs-rag/) for any security updates from the vendor. As a temporary control measure, implement operating system-level restrictions such as AppArmor or SELinux profiles to limit the commands that the mcp-docs-rag process can execute, or run the service in a restricted container with minimal privileges and no access to sensitive git repositories or system commands. Alternatively, consider using alternative implementations of git-based document retrieval that implement proper input sanitization.