Vulnerability Database · Hackage · git-annex · Version
git-annex 5.20150113
5.20150113 is affected by 4 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 0 Medium 0 Low 0 Unrated 4
-
Database updated 22/Oct/2026
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
git-annex 5.20150113 vulnerabilities
4 vulnerabilities cover git-annex 5.20150113. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2017-12976: git-annex Command Injection via Malicious SSH Hostname | N/A unrated | 6.20170818 | 25 Jul 2023 |
| CVE-2018-10857: git-annex private data exfiltration to compromised remote | N/A unrated | 6.20180626 | 25 Jul 2023 |
| Vulnerability in git-annex: Exposure of Checksum to Encrypted Special Remotes | N/A unrated | 6.20160419 | 25 Jul 2023 |
| CVE-2018-10859: git-annex GPG decryption attack via compromised remote | N/A unrated | 6.20180626 | 25 Jul 2023 |
Looking for another version, or everything Vulert holds for git-annex?
Questions
About git-annex 5.20150113
Is git-annex 5.20150113 vulnerable?
Yes. 4 vulnerabilities in the Vulert database cover git-annex 5.20150113: 0 critical, 0 high, 0 medium and 0 low, plus 4 not yet rated. Each entry above names the fixed version to move to.
How do I monitor git-annex for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the git-annex version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.