Gitblame Project maintains a command-line source-code analysis tool focused on blame and authorship attribution, with the observed vulnerability exposure centered on command-injection risks in input handling. The durable signal reflects the tool's interaction with shell and version-control processes, where improper neutralization of special elements can allow injection of unintended commands. Current severity, exploitation, and CVE counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Gitblame Project over time
Signals from CVEs in this vendor scope (1 CVEs).
1 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-28434CRITICAL This affects all versions of package gitblame. The injection point is located in line 15 in lib/gitblame.js. | Aug 2, 2022 | 9.8 | 31 | NO | NO |
Signals from CVEs in this vendor scope (1 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Gitblame Project.
Media articles that mention a CVE ID that affects a product developed by Gitblame Project — matched by CVE ID, not by vendor name.