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

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

code-mcp CVE-2026-7811

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

CVE-2026-7811 has a CVSS 4.0 base score of 5.5 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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.0%.

EUVD-2026-27215 MEDIUM

Path Traversal (CWE-22)

2026-05-05 VulDB

Path Traversal Code Mcp

5.5

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

May 05, 2026 - 05:30 vuln.today

Severity Changed

May 05, 2026 - 05:22 NVD

HIGH MEDIUM

CVSS changed

May 05, 2026 - 05:22 NVD

7.3 (HIGH) 5.5 (MEDIUM)

DescriptionCVE.org

A vulnerability has been found in 54yyyu code-mcp up to 4cfc4643541a110c906d93635b391bf7e357f4a8. The affected element is the function is_safe_path of the file src/code_mcp/server.py of the component MCP File Handler. Such manipulation leads to path traversal. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The project was informed of the problem early through an issue report but has not responded yet.

AnalysisAI

Path traversal vulnerability in 54yyyu code-mcp's MCP File Handler (function is_safe_path in src/code_mcp/server.py) allows remote unauthenticated attackers to access files outside intended directories with low confidentiality, integrity, and availability impact. Publicly available exploit code exists; the project uses rolling releases without versioned releases, and the vendor has not yet responded to early disclosure.

Technical ContextAI

The vulnerability exists in the is_safe_path function of the MCP File Handler component in code-mcp, which is responsible for validating file paths before operations. The flaw is classified as CWE-22 (Improper Limitation of a Pathname to a Restricted Directory, also known as path traversal). This occurs when user-supplied path input is not properly canonicalized or validated, allowing attackers to use directory traversal sequences (such as ../ or absolute paths) to reference files outside the intended base directory. The affected product uses a rolling release model without discrete version tagging, making version identification difficult; the vulnerability is present up to commit 4cfc4643541a110c906d93635b391bf7e357f4a8 in the 54yyyu/code-mcp repository.

RemediationAI

Immediate action: upgrade code-mcp to a version released after commit 4cfc4643541a110c906d93635b391bf7e357f4a8. Since the project uses rolling releases without version tags, monitor the GitHub repository (https://github.com/54yyyu/code-mcp/) for commits that address the path traversal in is_safe_path or pull requests closing issue #4 (https://github.com/54yyyu/code-mcp/issues/4). Pending a vendor fix, implement compensating controls: restrict network access to the code-mcp service using firewall rules or reverse-proxy authentication (trade-off: reduces usability if remote access is required); disable or remove the MCP File Handler component if not essential to your workflow; or run code-mcp in a sandboxed environment (chroot, container, or VM) with read-only mount of the filesystem (trade-off: limits functionality). The vulnerability is in path validation logic, so patching or code review should focus on hardening the is_safe_path function to prevent .. sequences and absolute path bypass.