# CVE-2021-26541: Command injection in gitlog


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 8 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-67mm-m3wx-j7fr

## What is CVE-2021-26541?

CVE-2021-26541 is a critical vulnerability in n/a, published on 8 Feb 2021. 

### Official description

The gitlog function in src/index.ts in gitlog before 4.0.4 has a command injection vulnerability.

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

## Which versions are affected by CVE-2021-26541?

2 open source packages ship an affected version, including gitlog. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlog` | npm | All versions | 4.0.4 |
| `gitlog` | npm | All versions | 4.0.4 |

Products: Gitlog Project Gitlog.

## How do I fix CVE-2021-26541?

Upgrade gitlog to 4.0.4 or later.

## Is CVE-2021-26541 being exploited?

There is no known exploitation of CVE-2021-26541 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-26541 and fix it if it is affected.

What it is: CVE-2021-26541 is a critical vulnerability in n/a, published on 8 Feb 2021. 
Exploitation: There is no known exploitation of CVE-2021-26541 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitlog (npm): affected all versions; fixed in 4.0.4
- gitlog (npm): affected all versions; fixed in 4.0.4

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

## Sources

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

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