Skip to content

AAK-MCP-REPOMIX-CVE-2026-49988-001: Repomix MCP server bypasses secret-scan file-read boundary (below 1.14.1)

Severity
MEDIUM
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
RepomixMcpSecretLintBypass

What it detects

Repomix before 1.14.1 lets the MCP server's attach_packed_output / read_repomix_output flow register and read arbitrary local .json / .txt / .md / .xml files without the file_system_read_file runSecretLint() safety check or packed-output validation, so MCP callers bypass the local file-read secret-scanning boundary and can read secrets Repomix would otherwise redact (CVE-2026-49988). Treat < 1.14.1 (and unpinned) as exposed.

How to fix

Upgrade repomix to >= 1.14.1 and pin it. Ensure every MCP file-read path runs the same secret-lint / output-validation checks as the direct read tool.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-REPOMIX-CVE-2026-49988-001

Limitations

Reads repomix in requirements*.txt at any depth and, at the project root only, in pyproject.toml, Pipfile, package.json, .mcp.json, mcp.json, claude_desktop_config.json and the Pipfile.lock, poetry.lock, uv.lock, package-lock.json, pnpm-lock.yaml and yarn.lock lockfiles, taking the lowest version a range allows and reporting a reference that states no version. The dependency is not read when it is declared in a sub-directory manifest (packages/app/package.json), in .cursor/mcp.json or .vscode/mcp.json, or in a lockfile format the reader does not parse (a Yarn 2+ yarn.lock). A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-REPOMIX-CVE-2026-49988-001.md: the page then shows that text, with the registry reference appended under it.