On this page (6 sections)

On November 2, 2026, the Debian security team published DSA-6603-1, a security update for git-annex, the tool used to manage large files with git without storing the file contents in git. The advisory says the vulnerability could result in data exfiltration and assigns it CVE-2026-112818.

If you run Debian 13 (trixie) servers, build machines or developer workstations that have git-annex installed, you should check the package version and update. Only one primary source (the Debian advisory) is available so far, so several details are still unknown, and this article marks them as such.

What happened

Debian's advisory describes a vulnerability in git-annex that could lead to data exfiltration, meaning data leaving a place where it was meant to stay. The advisory itself is short and points readers to the upstream git-annex advisory, titled "cross repository data exfiltration via special remote", on git-annex.branchable.com.

For the stable distribution, trixie, Debian says the problem is fixed in version 10.20250416-2+deb13u1 and recommends upgrading the git-annex packages. The advisory was posted by Moritz Muehlenhoff of the Debian security team.

What we know and what we do not

The Debian advisory gives the CVE, the fixed package version and a one-line impact statement. It does not give a CVSS score, an attack description, a list of vulnerable upstream versions, or any statement about exploitation. The research for this story also includes no CVE record from NVD or a GitHub advisory, and no CISA KEV entry.

  • Severity: unknown. Do not assume it is low or high; no score has been published in the material we reviewed.
  • Exploitation: not mentioned by Debian. Treat it as unconfirmed rather than as safe.
  • Other Debian releases: the advisory names only trixie. Check the Debian security tracker for the status of other releases.
  • Technical details: the title of the upstream advisory suggests the issue involves a special remote and data moving between repositories, but we have not seen the upstream text, so read it directly before drawing conclusions.

Who is realistically exposed

git-annex is a developer and data-management tool, not a web server component, so most public websites will not have it installed. The people most likely to be affected are teams that use it to handle large datasets, media archives or backups, and administrators of shared servers or CI systems where several repositories, possibly with different sensitivity levels, are handled by the same user or machine.

The upstream advisory title mentions cross-repository exfiltration, so environments that mix repositories of different trust levels deserve the most attention. That is an inference from the title only; confirm the exact conditions in the upstream advisory.

How to check your exposure

This command lists the installed git-annex package and its version on Debian or Ubuntu-based systems. If it reports that no packages match, git-annex is not installed through apt. On trixie, a version older than 10.20250416-2+deb13u1 needs the update.

Check the installed git-annex package version (Debian/Ubuntu)Shell
dpkg -l git-annex

This shows the installed and candidate versions from your configured repositories, so you can see whether the fixed version is available to you.

Compare installed and available versions (Debian/Ubuntu)Shell
apt policy git-annex

If you installed git-annex some other way, such as a standalone binary or a build from source, the Debian package check will not cover it. Check your install method and compare against the upstream advisory.

What to do now

  1. Find every Debian trixie host, build runner and workstation with git-annex installed (use dpkg -l git-annex).
  2. Refresh package lists and upgrade git-annex to 10.20250416-2+deb13u1 or later.
  3. Confirm the new version with dpkg -l git-annex or apt policy git-annex.
  4. Read the upstream git-annex advisory and the Debian security tracker page for git-annex to understand the conditions and any other affected releases.
  5. Review which repositories and special remotes are configured on shared systems, and remove any you no longer need.
  6. If you manage non-Debian systems or standalone installs, check the upstream project for fixed releases and update those separately.

This command refreshes the package lists and upgrades only the git-annex package on Debian. It does not restart anything by itself. Afterwards, check that the version shown by dpkg -l git-annex is 10.20250416-2+deb13u1 or later.

Upgrade only git-annex (Debian trixie, run as root or with sudo)Shell
sudo apt update
sudo apt install --only-upgrade git-annex
Caution. Processes that were already running before the upgrade keep using the old code until they are restarted. If git-annex runs as a background job on a production system, restart it during a quiet period so you do not interrupt a transfer in progress.

Detection and monitoring afterwards

Debian does not describe indicators of compromise for this flaw, so there is no known log signature to search for. A practical approach is to review what data your git-annex setups could reach: which remotes are configured, which credentials they use, and what outbound connections those hosts normally make. Unexpected transfers to storage endpoints you do not recognize are worth investigating regardless of this CVE.

Keep an eye on the Debian security tracker for git-annex and on Debian's announcement list, since details, scores or fixes for other releases may be added after the first advisory. Debian published other security updates in the same period, so it is worth checking the rest of your pending package updates in the same maintenance window. For a broader routine, our small business website security guide covers keeping server software patched, and our security news archive tracks other Debian advisories.

If you run a public website on the same servers, the free security headers checker is useful general hygiene, though it will not tell you whether a developer tool like git-annex is installed.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. [SECURITY] [DSA 6603-1] git-annex security updatelists.debian.org ·
  • Debian
  • git-annex
  • DSA
  • CVE-2026-112818
  • patching