dbcve.org
RepomixApplication · Yamadashy

CVE-2026-49988

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-15
Fix available
A fix is available. Upgrade to 1.14.1 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click 5 weeks old

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
Repomix is a tool that packs repositories into AI-friendly files. Prior to 1.14.1, the Repomix MCP server attach_packed_output and read_repomix_output flow can register and read arbitrary local .json, .txt, .md, or .xml files without the file_system_read_file runSecretLint() safety check or Repomix packed-output validation, allowing MCP callers to bypass the local file-read secret-scanning boundary. This issue is fixed in version 1.14.1.

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 · high confidence

Repomix MCP server versions prior to 1.14.1 have a path traversal vulnerability in the attach_packed_output and read_repomix_output functions that allows reading arbitrary local .json, .txt, .md, or .xml files. These functions bypass the file_system_read_file runSecretLint() safety check and Repomix packed-output validation, enabling MCP callers to circumvent the local file-read secret-scanning boundary.

MitigationUpgrade to Repomix version 1.14.1 or later, which reinstates the proper file_system_read_file runSecretLint() safety check and Repomix packed-output validation to prevent unauthorized local file access.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RepomixApplication
Affected:< 1.14.1

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
High
Integrity
None
Availability
None

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

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 Repomix MCP server version
    Run 'npm list repomix-mcp-server' or check package.json in your project to find the installed repomix-mcp-server version. If using a global installation, check 'npm list -g repomix-mcp-server'.
    Affected if The installed version is prior to 1.14.1 (e.g., 1.14.0, 1.13.x, or older)
  2. Confirm MCP server is running
    Check if the Repomix MCP server process is active. Look for the server running on its configured port (typically via ps aux, docker ps, or your MCP client status).
    Affected if The MCP server is running and accessible to untrusted callers
  3. Verify MCP tool exposure
    Inspect your MCP client configuration to confirm the 'attach_packed_output' and 'read_repomix_output' tools are exposed and callable. Check the server's tool definitions if accessible.
    Affected if These tools are exposed and callable by MCP clients without additional authorization checks
  4. Test for path traversal accessibility
    If you have access to invoke MCP tools, attempt a benign test: call read_repomix_output with a path pointing outside the expected Repomix output directory (e.g., ../../package.json). Observe if arbitrary file content is returned.
    Affected if The tool returns contents of files outside the intended output directory, confirming the path traversal is exploitable

You are affected if the Repomix MCP server version is prior to 1.14.1 and the MCP tools are accessible to callers who should not have arbitrary file read access.

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.

dbcve · scoped
Upgrade available Upgrade to 1.14.1 or later
Fixed in 1.14.1
Interim mitigation

Upgrade to Repomix version 1.14.1 or later, which reinstates the proper file_system_read_file runSecretLint() safety check and Repomix packed-output validation to prevent unauthorized local file access.

Recommended fix High confidence

1.14.1

  1. Identify the package manager used to install Repomix (npm, yarn, or pnpm)
  2. Run the package manager upgrade command to update to version 1.14.1: npm install [email protected] (or yarn add [email protected], or pnpm add [email protected])
  3. If using Repomix as a dependency in a project, update the version in package.json to ^1.14.1 or the specific version 1.14.1
  4. Run npm install or the equivalent to update the dependency lockfile
  5. Verify the installed version by running: npx repomix --version
  6. Restart any running Repomix MCP server instances to ensure the patched version is loaded

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Repomix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49988 — 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-49988 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