# CVE-2018-10857: Information disclosure in git-annex

> Attackers can expose content of files outside the repository or from private local web servers via git-annex.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-10857, GHSA-f7cm-x4r7-4852, HSEC-2023-0010, UBUNTU-CVE-2018-10857

## What is CVE-2018-10857?

CVE-2018-10857 is a medium-severity vulnerability in Debian Debian Linux, published on 16 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

git-annex is vulnerable to a private data exposure and exfiltration attack. It could expose the content of files located outside the git-annex repository, or content from a private web server on localhost or the LAN.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-10857?

1 open source package ship an affected version, including git-annex. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `git-annex` | Hackage | All versions | 6.20180626 |

Products: Debian Debian Linux, Git-Annex Project Git-Annex.

## How do I fix CVE-2018-10857?

Upgrade git-annex to 6.20180626 or later.

## Is CVE-2018-10857 being exploited?

There is no known exploitation of CVE-2018-10857 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10857 and fix it if it is affected.

What it is: CVE-2018-10857 is a medium-severity vulnerability in Debian Debian Linux, published on 16 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-10857 in the wild and no public exploit code.

Affected packages and fixed versions:
- git-annex (Hackage): affected all versions; fixed in 6.20180626

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/CVE-2018-10857/ (Markdown: https://insights.sbomify.com/CVE-2018-10857/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-10857
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-10857
- OSV: https://osv.dev/vulnerability/CVE-2018-10857

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