CVE-2026-49987
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRepomix 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceRepomix versions prior to 1.14.1 contain a Git option injection vulnerability in the execGitShallowClone function within src/core/git/gitCommand.ts. The --remote-branch parameter is passed directly to git fetch and git checkout commands without validation or the --end-of-options delimiter, allowing injection of arbitrary git options such as --upload-pack to execute commands through local or SSH-style transports, bypassing the validateGitUrl() dangerous parameter checks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.14.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Repomix versionRun 'repomix --version' or 'repomix -v' in your terminal. If installed as an npm package, check the version in package.json or run 'npm list repomix'.Affected if The version is below 1.14.1 (e.g., 1.14.0, 1.13.0, etc.)
-
Verify git remote repository usageInspect your Repomix configuration or command-line usage to determine if you are processing remote git repositories. The vulnerable code path (execGitShallowClone) is only triggered when cloning from remote sources.Affected if You are running Repomix against remote git repositories (HTTP/HTTPS/SSH URLs) as opposed to only local directories.
-
Confirm git command execution contextReview the Repomix execution logs or run with verbose/debug output to confirm that git fetch and git checkout commands are being invoked with the --remote-branch parameter.Affected if Git operations are being performed with a remote-branch argument, which passes user input directly to git commands without the --end-of-options delimiter.
You are affected if you are using Repomix version 1.14.0 or earlier AND processing remote git repositories, as the --remote-branch parameter can be injected with arbitrary git options.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.14.1
Upgrade to Repomix version 1.14.1 or later, which implements proper input validation and uses the --end-of-options delimiter to prevent git option injection.
1.14.1
- Upgrade Repomix to version 1.14.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49987 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49987 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data