Information Disclosure in repomix (CVE-2026-49988)
Summary
Vulnerability in repomix (CVE-2026-49988). Confidential information can be exposed externally. Exploitable via attach_packed_output. Mitigation: upgrade to 1.14.1 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49988 has been found in repomix.
Attackers can target a specific entry point like attach_packed_output over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade repomix to 1.14.1 or later.
If unsure, ask your IT team or search "repomix CVE-2026-49988" on the vendor's site.
CVE-2026-49988 (repomix) — CWE-200 / CVSS v3 5.5
Attack vector: local / no user interaction
Attack surface: attach_packed_output / file_system_read_file / read_repomix_output / outputId
Patched: 1.14.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in repomix. Attackers reach the vulnerable code path via attach_packed_output.
Check the vendor advisory for the affected versions of repomix. Attack surface: attach_packed_output / file_system_read_file / read_repomix_output / outputId.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to 1.14.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'repomix' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'repomix' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
repomixを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade repomix to 1.14.1ステージング環境で 1.14.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com