PatchTheCVECVE-2023-26134: Versions of the package git-commit-info before 2.0.2 are vulnerable to Command Injection such that the package
CVE-2023-26134 is a critical-severity flaw (CVSS 9.8) affecting git-commit-info. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2023-26134?
git-commit-info: upgrade to 2.0.2. Exact commands for each OS are on this page.
Is CVE-2023-26134 being exploited?
CVE-2023-26134 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2023-26134 affect?
CVE-2023-26134 affects git-commit-info. Severity is critical (CVSS 9.8). 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
How urgent is CVE-2023-26134?
Priority 67/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action