dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-5023

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in DeDeveloper23 codebase-mcp up to 3ec749d237dd8eabbeef48657cf917275792fde6. This vulnerability affects the function getCodebase/getRemoteCodebase/saveCodebase of the file src/tools/codebase.ts of the component RepoMix Command Handler. Such manipulation leads to os command injection. The attack needs to be performed locally. The exploit has been disclosed to the public and may be used. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

OS command injection vulnerability in the RepoMix Command Handler of codebase-mcp. The functions getCodebase, getRemoteCodebase, and saveCodebase in src/tools/codebase.ts accept input that is passed to system shell commands without proper sanitization, allowing an attacker to execute arbitrary OS commands locally.

MitigationImplement strict input validation and use safe API alternatives that avoid shell command execution. If shell commands are necessary, use parameterized approaches and whitelist validation for all user-controlled input.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify codebase-mcp installation
    Run 'npm list codebase-mcp' or check your node_modules for the codebase-mcp package directory
    Affected if The package is not installed or the directory does not exist
  2. Check codebase-mcp version
    Run 'npm list codebase-mcp --depth=0' to see the installed version, or check package.json dependencies
    Affected if The installed version matches or precedes the vulnerable range (any version prior to patched release)
  3. Locate vulnerable source file
    Check for the presence of src/tools/codebase.ts in the codebase-mcp installation directory
    Affected if The file exists and contains the getCodebase, getRemoteCodebase, or saveCodebase functions
  4. Verify shell command usage
    Inspect src/tools/codebase.ts and search for patterns like exec(), spawn(), or shell command invocations that use user-supplied variables without sanitization (e.g., backticks, $() with string concatenation)
    Affected if The code uses shell execution methods (exec, spawn, execSync) with unsanitized input parameters
  5. Confirm tool exposure
    Check your MCP server configuration or running instance to see if the codebase tools (getCodebase, getRemoteCodebase, saveCodebase) are registered and accessible to clients
    Affected if Any of these three functions are exposed as callable tools via the MCP protocol

You are affected if codebase-mcp is installed, the vulnerable codebase.ts file exists with unsanitized shell command execution, and the affected functions are exposed for use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and use safe API alternatives that avoid shell command execution. If shell commands are necessary, use parameterized approaches and whitelist validation for all user-controlled input.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5023 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5023 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data