VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

git-annex: vulnerability history, versions and safety

git-annex is a package in the Debian ecosystem. Vulert records 2 vulnerabilities for it across 2 releases, from Oct 2017 to Sep 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded U2
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.

See all git-annex vulnerabilities

Vulert verdict on git-annex i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 2 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 2 over 1 year · 0 in the last year i
  • Latest disclosure 05 Sep 2018 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
5.20141125 U2 Yes Details →
5.20141125+deb8u1 U1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2018 1

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

03 Vulnerabilities

Recorded vulnerabilities for git-annex

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Security Vulnerabilities in git-annex Package N/A unrated 5.20141125+oops-1+deb8u2 05 Sep 2018
Security Update for git-annex N/A unrated 5.20141125+deb8u1 30 Oct 2017

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

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 2 vulnerabilities for git-annex in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 2 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?

2 vulnerabilities are recorded for git-annex in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 2 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 30 Oct 2017. 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.