Quick answers
- Is CVE-2026-7211 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7211 being exploited in the wild.
- How severe is CVE-2026-7211?
- High severity, with a CVSS score of 7.3, published 28 April 2026.
- Which products and versions are affected?
- dvladimirov MCP 0.1.0.
- Is there a fix for CVE-2026-7211?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-7211 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-7211?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A command injection vulnerability exists in the `GitSearchRequest` function within `mcp_server.py` of the dvladimirov MCP project (up to version 0.1.0). The root cause is the improper neutralization of the `repo_url` and `pattern` arguments, which are interpolated into a shell command string using Python f-strings and executed via `subprocess.check_output` with `shell=True`. Specifically, the `search_repository` method in `mcp/git_service.py` passes the raw user-supplied pattern to a `grep` command. A remote, unauthenticated attacker can exploit this by sending a specially crafted POST request to the `/v1/models/git-analyzer/search` endpoint containing shell metacharacters (e.g., `;` or `"`). This allows for arbitrary code execution on the host operating system. As of the advisory date, no official patch has been released.
Affected products
- dvladimirov MCP 0.1.0
Timeline
- 2026-04-10: disclosed: Vulnerability reported to the vendor via GitHub issue
- 2026-04-28: advisory: NVD/VulDB advisory published