Vulnerability Database · Hackage · Package report

git-annex: vulnerability history, versions and safety

git-annex is a package in the Hackage ecosystem. Vulert records 5 vulnerabilities for it across 120 releases, first recorded in Jul 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded U5
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on git-annex i

Updated on 22 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 25 Jul 2023. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 5 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 5 over 1 year · 0 in the last year i
  • Latest disclosure 25 Jul 2023 i
  • Highest CVSS n/a i
  • With no published fix 0 i

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 Versions

Which versions are affected

Every version Vulert holds for git-annex, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
6.20180529 U2 Yes Details →
6.20180509 U2 Yes Details →
6.20180427 U2 Yes Details →
6.20180409 U2 Yes Details →
6.20180316 U2 Yes Details →
6.20180227 U2 Yes Details →
6.20180112 U2 Yes Details →
6.20171214 U2 Yes Details →
6.20171124 U2 Yes Details →
6.20171109 U2 Yes Details →
6.20171026 U2 Yes Details →
6.20171018 U2 Yes Details →
6.20171003 U2 Yes Details →
6.20170925 U2 Yes Details →
6.20170818 U2 Yes Details →
6.20170520 U3 Yes Details →
6.20170519 U3 Yes Details →
6.20170510 U3 Yes Details →
6.20170321 U3 Yes Details →
6.20170301.1 U3 Yes Details →
6.20170301 U3 Yes Details →
6.20170214 U3 Yes Details →
6.20170101 U3 Yes Details →
6.20161210 U3 Yes Details →
6.20161118 U3 Yes Details →
6.20161111 U3 Yes Details →
6.20161031 U3 Yes Details →
6.20161027 U3 Yes Details →
6.20161012 U3 Yes Details →
6.20160923 U3 Yes Details →
6.20160907 U3 Yes Details →
6.20160808 U3 Yes Details →
6.20160619 U3 Yes Details →
6.20160613 U3 Yes Details →
6.20160527 U3 Yes Details →
6.20160511 U3 Yes Details →
6.20160419 U3 Yes Details →
6.20160418 U4 Yes Details →
6.20160412 U4 Yes Details →
6.20160318 U4 Yes Details →
6.20160229 U4 Yes Details →
6.20160211 U4 Yes Details →
6.20160126 U4 Yes Details →
6.20160114 U4 Yes Details →
5.20151218 U4 Yes Details →
5.20151208 U4 Yes Details →
5.20151116 U4 Yes Details →
5.20151102.1 U4 Yes Details →
5.20151102 U4 Yes Details →
5.20151019 U4 Yes Details →
5.20150930 U4 Yes Details →
5.20150916 U4 Yes Details →
5.20150824 U4 Yes Details →
5.20150812 U4 Yes Details →
5.20150731 U4 Yes Details →
5.20150727 U4 Yes Details →
5.20150710 U4 Yes Details →
5.20150617 U4 Yes Details →
5.20150528 U4 Yes Details →
5.20150522 U4 Yes Details →
5.20150508.1 U4 Yes Details →
5.20150508 U4 Yes Details →
5.20150420 U4 Yes Details →
5.20150409 U4 Yes Details →
5.20150406.1 U4 Yes Details →
5.20150406 U4 Yes Details →
5.20150327 U4 Yes Details →
5.20150317 U4 Yes Details →
5.20150219 U4 Yes Details →
5.20150205 U4 Yes Details →
5.20150113 U4 Yes Details →
5.20141231 U4 Yes Details →
5.20141219 U4 Yes Details →
5.20141203 U4 Yes Details →
5.20141125 U4 Yes Details →
5.20141024 U4 Yes Details →
5.20141013 U4 Yes Details →
5.20140927 U4 Yes Details →
5.20140926 U4 Yes Details →
5.20140919 U4 Yes Details →
5.20140915 U5 Yes Details →
5.20140831 U5 Yes Details →
5.20140817 U5 Yes Details →
5.20140717 U5 Yes Details →
5.20140709 U5 Yes Details →
5.20140707 U5 Yes Details →
5.20140613 U5 Yes Details →
5.20140606 U5 Yes Details →
5.20140529 U5 Yes Details →
5.20140517 U5 Yes Details →
5.20140421 U5 Yes Details →
5.20140412 U5 Yes Details →
5.20140405 U5 Yes Details →
5.20140402 U5 Yes Details →
5.20140320 U5 Yes Details →
5.20140306 U5 Yes Details →
5.20140227 U5 Yes Details →
5.20140221 U5 Yes Details →
5.20140210 U5 Yes Details →
5.20140129 U5 Yes Details →
5.20140127 U5 Yes Details →
5.20140116 U5 Yes Details →
5.20140108 U5 Yes Details →
5.20140107 U5 Yes Details →
5.20131230 U5 Yes Details →
5.20131221 U5 Yes Details →
5.20131213 U5 Yes Details →
5.20131130 U5 Yes Details →
5.20131127 U5 Yes Details →
5.20131120 U5 Yes Details →
5.20131118 U5 Yes Details →
4.20131106 U5 Yes Details →
4.20131101 U5 Yes Details →
4.20131024 U5 Yes Details →
4.20131002 U5 Yes Details →
4.20130927 U5 Yes Details →
4.20130920 U5 Yes Details →
4.20130909 U5 Yes Details →
4.20130827 U5 Yes Details →
4.20130815 U5 Yes Details →

Newest 120 of 192 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 5

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 5 were recorded in the last 12 months.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About git-annex

Is git-annex safe to use?

Vulert records 5 vulnerabilities for git-annex in Hackage: 0 critical, 0 high, 0 medium and 0 low, plus 5 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does git-annex have?

5 vulnerabilities are recorded for git-annex in the Hackage ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 5 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new git-annex vulnerabilities disclosed?

0 vulnerabilities were recorded for git-annex in the last 12 months, and the oldest entry in this database dates to 25 Jul 2023. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of git-annex are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.