Repomix vulnerabilities
4 known CVE vulnerabilities in Repomix, translated and rated.
- CVE-2026-59702Critical
Repomix contains a server-side request forgery (SSRF) vulnerability in the POST /api/pack endpoint that allows unauthenticated attackers to make arbitrary outbound requests. The endpoint fails to properly validate http://, https://, and file:// URLs before passing them to git clone, enabling attackers to access private network addresses, GCP metadata services, or local filesystem paths.
- CVE-2026-49988Medium
Repomix MCP server before version 1.14.1 allows registering and reading arbitrary local .json, .txt, .md, or .xml files without the file_system_read_file runSecretLint() safety check or Repomix packed-output validation. This enables MCP callers to bypass the local file-read secret-scanning boundary.
- CVE-2026-49987High
Repomix prior to version 1.14.1 contains a vulnerability in the execGitShallowClone function where the --remote-branch parameter is passed directly to git fetch and git checkout without validation or --end-of-options. This allows injection of Git options like --upload-pack, bypassing validateGitUrl() checks and enabling command execution via local or SSH transports.
- CVE-2026-59703High
Repomix contains a local file inclusion vulnerability in the git clone endpoint that allows unauthenticated attackers to read arbitrary local git repositories. The isValidRemoteValue function in src/core/git/gitRemoteParse.ts fails to block file:// URLs, permitting attackers to supply file:// scheme URLs that bypass validation and are passed directly to git clone, enabling unauthorized access to all tracked file contents on the server filesystem.

