Skip to content

← Public intelligence

npm package

repomix

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.9npmAmendedPublished

    repomix: attach_packed_output can bypass file-read secret scanning for supported local files

    CVE-2026-49988 · GHSA-hwpp-h97w-2h3j

    Affected
    • npm repomix <= 1.14.0
    Fixed in
    1.14.1· Vendor fix available
    Issue
    attachpackedoutput can register arbitrary .json/.txt/.md/.xml files and bypass the MCP file-read safety check Summary Repomix's MCP server exposes a normal filesystemreadfile tool that reads absolute paths only after running the project's secret check. However, the attachpackedoutput plus readrepomixoutput flow can read arbitrary local .json, .txt, .md, or .xml files without the same safety check and without verifying that the file is actually a Repomix packed output. This is a medium-severity local MCP file-read boundary issue. The affected deployment is the documented repomix --mcp stdio server used by AI assistants. A prompt or lower-trust model action that can invoke MCP tools can use attachpackedoutput on a local JSON/text file, receive an outputId, then call readrepomixoutput to retrieve the full file content. Affected target - Repository: yamadashy/repomix - Commit reviewed: adf5a12f2211a7fabf24ee11a21734adccee5143 - Component: MCP server tools - Package version reviewed:…

    Recommended action: Upgrade to 1.14.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 8.8npmAmendedPublished

    repomix Vulnerable to Command Injection (RCE) via --remote-branch Argument Injection

    CVE-2026-49987 · GHSA-9mm9-rqhj-j5mx

    Affected
    • npm repomix < 1.14.1
    Fixed in
    1.14.1· Vendor fix available
    Issue
    Vulnerability Metadata | Field | Detail | | --- | --- | | Affected Component | src/core/git/gitCommand.ts (execGitShallowClone) | | Impact | Arbitrary Command Execution / Security Control Bypass | Summary The --remote-branch CLI option in repomix is vulnerable to argument injection. User-supplied input is passed directly to git fetch and git checkout subprocesses via childprocess.execFileAsync without sanitization, -- delimiters, or validation. An attacker can inject arbitrary git command-line options. By injecting the --upload-pack option and specifying an SSH (git@...) or local (file://) remote URL, an attacker achieves arbitrary command execution with the privileges of the user running repomix. This bypasses the existing dangerousParams blocklist implemented in validateGitUrl(). Vulnerable Code Analysis File: src/core/git/gitCommand.ts The remoteBranch parameter is appended directly to the arguments array for git subprocesses without the -- positional delimiter. Sink 1 (Lines…

    Recommended action: Upgrade to 1.14.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →