CVE-2026-106764 @rog0x/mcp-git-tools executes arbitrary code via the resolveBaseBranch function
High 7.5
Published
Updated
Check this codebase for CVE-2026-106764 and fix it if it is affected.
What it is: CVE-2026-106764 is a high-severity vulnerability in n/a, published on 23 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-106764 in the wild and no public exploit code.
Affected packages and fixed versions:
- @rog0x/mcp-git-tools (npm): affected all versions up to 1.0.1; no fix listed
- @rog0x/mcp-git-tools (npm): affected all versions up to 1.0.1; no fix listed
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-106764/ (Markdown: https://insights.sbomify.com/CVE-2026-106764/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-106764?
CVE-2026-106764 is a high-severity vulnerability in n/a, published on 23 Oct 2026.
Official description
An issue in @rog0x/mcp-git-tools 1.0.1 allows a remote attacker to execute arbitrary code via the resolveBaseBranch function.
Weakness: CWE-94
Which versions are affected by CVE-2026-106764?
2 open source packages ship an affected version, including @rog0x/mcp-git-tools.
| Package | Affected | Fixed in |
|---|---|---|
@rog0x/mcp-git-tools npm | All versions to 1.0.1 | None |
@rog0x/mcp-git-tools npm | All versions to 1.0.1 | None |
How do I fix CVE-2026-106764?
No fix has been published for CVE-2026-106764 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-106764 being exploited?
There is no known exploitation of CVE-2026-106764 in the wild and no public exploit code.
Sources
Also known as GHSA-jwc4-922r-f2rw.