Skip to main content
Menu
CVEs

CVE

code-review-mcp-server command injection in MCP tool parameters

Affects code-review-mcp-server versions before 1.5.3 that expose the getLocalGitDiff, codeReview, createPR or getPRTemplate MCP tools. Fixed in 1.5.3.

CVE-2026-68934EUVD-2026-126705

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

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

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.5.3
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Version before 1.5.3 of code-review-mcp-server The server exposes the getLocalGitDiff, codeReview, createPR or getPRTemplate MCP tools

Published
Last modified
Reference
Last checked
18/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

The Orcus2021 code-review-mcp-server package lets an attacker run arbitrary commands with the privileges of the host process by injecting shell metacharacters through the folderPath and baseBranch parameters of several MCP tools. An attacker can do this remotely over the network with low-privileged access and no user action.

Original description

code-review-mcp-server automates code review and can post comments directly on GitHub pull requests. Prior to 1.5.3, the getLocalGitDiff, codeReview, createPR, and getPRTemplate MCP tools accept caller-controlled folderPath and baseBranch string parameters that are interpolated into command strings executed by child_process.execSync through /bin/sh. Shell metacharacters, command substitution, or quote-breaking input can therefore execute arbitrary commands with the privileges of the host process running the MCP server. This issue is fixed in version 1.5.3.

Who should check

Anyone running the code-review-mcp-server npm package before 1.5.3 as an MCP server exposing getLocalGitDiff, codeReview, createPR or getPRTemplate.

“code-review-mcp-server exposes MCP tools ( getLocalGitDiff , codeReview , createPR , getPRTemplate )”

github.com

cve.now Index

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.7/10CVSS 8.7, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Version before 1.5.3 of code-review-mcp-server The server exposes the getLocalGitDiff, codeReview, createPR or getPRTemplate MCP tools
  • Upgrade to a fixed version: 1.5.3.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-68934 (code-review-mcp-server: Command injection via unsanitized folderPath/baseBranch parameters), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-68934 (entry last updated 2026-11-16):
Affected:
- Orcus2021 code-review-mcp-server: fixed in 1.5.3
Fixed versions: 1.5.3.
Conditions (all must be true for the bug to be hit):
- Version before 1.5.3 of code-review-mcp-server (source: https://github.com/Orcus2021/code-review-mcp-server/security/advisories/GHSA-jq3q-62jc-fqq9)
- The server exposes the getLocalGitDiff, codeReview, createPR or getPRTemplate MCP tools (source: https://github.com/Orcus2021/code-review-mcp-server/security/advisories/GHSA-jq3q-62jc-fqq9)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-68934 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-68934 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Orcus2021/code-review-mcp-server/security/advisories/GHSA-jq3q-62jc-fqq9
- https://github.com/Orcus2021/code-review-mcp-server/issues/56
- https://github.com/Orcus2021/code-review-mcp-server/pull/57
- https://github.com/Orcus2021/code-review-mcp-server/commit/d11642322b607556affaaa3fd631d4f8942c05d8
- https://github.com/Orcus2021/code-review-mcp-server/releases/tag/v1.5.3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-68934
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-68934"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • Orcus2021 code-review-mcp-server

    fixed in 1.5.3

Evidence 7

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Repository
  2. Repository
  3. Repository
  4. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-68934

Is CVE-2026-68934 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Unsanitized folderPath and baseBranch values are passed into shell commands, so a crafted value can run arbitrary commands on the host running the MCP server.Source: github.com

Which versions are affected by CVE-2026-68934?

code-review-mcp-server: before 1.5.3.Source: cve.now feed data

Am I affected, and how do I check?

Versions before 1.5.3 of code-review-mcp-server are affected, but only where the server exposes the getLocalGitDiff, codeReview, createPR or getPRTemplate MCP tools. Check the installed version of code-review-mcp-server and whether those tools are exposed in your MCP setup.Source: github.com

How do I fix CVE-2026-68934?

Upgrade code-review-mcp-server to version 1.5.3 or later, which replaces every execSync() call with execFileSync().Source: github.com