PatchTheCVEgitblame vulnerabilities and fixes
Recent CVEs affecting gitblame, with upgrade or downgrade steps. 1 tracked.
gitblame has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2022-08-02. Highest priority: CVE-2020-28434 (score 61/100).
- CVE-2020-28434 CRITICAL 9.4 MITIGATE This affects all versions of package gitblame
FAQ
How do I fix gitblame vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is gitblame being exploited right now?
None of the tracked gitblame CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which gitblame CVE should I patch first?
CVE-2020-28434 currently ranks highest (61/100): This affects all versions of package gitblame.