# HSEC-2023-0012: git-annex checksum exposure to encrypted special remotes

> An attacker with access to an encrypted special remote can obtain file checksums during resumed uploads, leaking metadata about unencrypted files.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Nov 2025

## What is HSEC-2023-0012?

HSEC-2023-0012 is a vulnerability in git-annex, published on 14 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

# *git-annex* checksum exposure to encrypted special remotes

A bug exposed the checksum of annexed files to encrypted special
remotes, which are not supposed to have access to the checksum of
the un-encrypted file.  This only occurred when resuming uploads to
the encrypted special remote, so it is considered a low-severity
security hole.

For details, see commit `b890f3a53d936b5e40aa9acc5876cb98f18b9657`.

No CVE was assigned for this issue.

Fixed in *git-annex-6.20160419*.

## Which versions are affected by HSEC-2023-0012?

1 open source package ship an affected version, including git-annex.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `git-annex` | Hackage | From 0.20110417 | 6.20160419 |

## How do I fix HSEC-2023-0012?

Upgrade git-annex to 6.20160419 or later.

## Is HSEC-2023-0012 being exploited?

There is no known exploitation of HSEC-2023-0012 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for HSEC-2023-0012 and fix it if it is affected.

What it is: HSEC-2023-0012 is a vulnerability in git-annex, published on 14 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of HSEC-2023-0012 in the wild and no public exploit code.

Affected packages and fixed versions:
- git-annex (Hackage): affected from 0.20110417; fixed in 6.20160419

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/HSEC-2023-0012/ (Markdown: https://insights.sbomify.com/HSEC-2023-0012/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/HSEC-2023-0012

---
From sbomify Insights: https://insights.sbomify.com/HSEC-2023-0012/
Summaries are generated and may contain mistakes; the official description above is the record.