Skip to main content
VulnerabilityPublished

CVE-2026-68934: code-review-mcp-server · Command injection via unsanitized folderPath/baseBranch parameters

Affects code-review-mcp-serverSource GCVE Database

0
Compare
Authoritative record:CVE-2026-68934· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 1.5.3 soon.

Data as of 16 Nov 2026, 23:12 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.7
Patch
Available – fixed in 1.5.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade code-review-mcp-server to 1.5.3.

Affected software

ProductAffectedFixed in
npmcode-review-mcp-serverAffected
  • <1.5.3
Fixed in
  • 1.5.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade code-review-mcp-server to version 1.5.3 or later, where the vulnerability is fixed by replacing execSync() calls with execFileSync() and passing arguments without shell interpretation. No workarounds are available. Applying the official patch is the only recommended remediation.

Description

code-review-mcp-server versions prior to 1.5.3 contain a command injection vulnerability in several MCP tools that accept folderPath and baseBranch parameters. These parameters are unsafely interpolated into shell commands executed via child_process.execSync(), allowing an attacker to execute arbitrary commands on the host. The issue is fixed in version 1.5.3 by replacing execSync() calls with execFileSync() and passing arguments directly to git/gh without shell interpretation.

References

Community reviews

Loading reviews…