CVE-2026-49987

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 51% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Repomix is a tool that packs repositories into AI-friendly files. Prior to 1.14.1, src/core/git/gitCommand.ts execGitShallowClone passes the --remote-branch value directly to git fetch and git checkout without validation or --end-of-options, allowing --upload-pack or other Git option injection that bypasses validateGitUrl() dangerous parameter checks and can execute commands through local or SSH-style transports. This issue is fixed in version 1.14.1.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track*)
EG Risk 50/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
39.6%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 15, 2026

Advisory Details (3)

Auto-updated Jul 15, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Command Injection (RCE) via `--remote-branch` Argument Injection · Advisory · yamadashy/repomix · GitHub

https://github.com/yamadashy/repomix/security/advisories/GHSA-9mm9-rqhj-j5mx
github_release Patch Available

v1.14.1

Patch available: yamadashy/repomix v1.14.1

https://github.com/yamadashy/repomix/releases/tag/v1.14.1
github_commit Patch Available

commit 92bfa3193b52 (yamadashy/repomix)

Patch available: yamadashy/repomix v1.14.1 (contains commit 92bfa3193b52)

https://github.com/yamadashy/repomix/commit/92bfa3193b5233a0d21beff929444153c088de82

Vendor Advisories for CVE-2026-49987(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
repomix1.14.1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:18 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-15 20:53 UTCEG score recompute 1.30
  13. 2026-07-15 18:23 UTCMITRE cvelistV5CVSS v3 → 7.5 · CVSS v4 → 7.5
  14. 2026-07-01 19:02 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-49987?
CVE-2026-49987 is a high vulnerability published on July 1, 2026. Repomix is a tool that packs repositories into AI-friendly files. Prior to 1.14.1, src/core/git/gitCommand.ts execGitShallowClone passes the --remote-branch value directly to git fetch and git checkout without validation or --end-of-options, allowing --upload-pack or other Git option injection that…
When was CVE-2026-49987 disclosed?
CVE-2026-49987 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49987 actively exploited?
CVE-2026-49987 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49987?
CVE-2026-49987 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-49987?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49987, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49987

Explore →

Is Your Infrastructure Affected by CVE-2026-49987?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.