# CVE-2023-26134: git-commit-info vulnerable to Command Injection

> Attackers can execute arbitrary commands by injecting malicious content into the commit hash parameter of the git-commit-info library.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jun 2023
- **Updated:** 27 Nov 2024
- **Also known as:** GHSA-h42j-mrmp-9369

## What is CVE-2023-26134?

CVE-2023-26134 is a critical command injection vulnerability in git-commit-info, published on 28 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of the package git-commit-info before 2.0.2 are vulnerable to Command Injection such that the package-exported method gitCommitInfo () fails to sanitize its parameter commit, which later flows into a sensitive command execution API. As a result, attackers may inject malicious commands once they control the hash content.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2023-26134?

2 open source packages ship an affected version, including git-commit-info. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `git-commit-info` | npm | All versions | 2.0.2 |
| `git-commit-info` | npm | All versions | 2.0.2 |

Products: Git-Commit-Info Project Git-Commit-Info.

## How do I fix CVE-2023-26134?

Upgrade git-commit-info to 2.0.2 or later.

## Is CVE-2023-26134 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26134 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26134 and fix it if it is affected.

What it is: CVE-2023-26134 is a critical command injection vulnerability in git-commit-info, published on 28 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26134 exists.

Affected packages and fixed versions:
- git-commit-info (npm): affected all versions; fixed in 2.0.2
- git-commit-info (npm): affected all versions; fixed in 2.0.2

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-2023-26134/ (Markdown: https://insights.sbomify.com/CVE-2023-26134/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-26134
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-26134
- OSV: https://osv.dev/vulnerability/CVE-2023-26134

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-26134/
Summaries are generated and may contain mistakes; the official description above is the record.