# CVE-2026-44647: OneDev: Path Traversal (read capability via Git LFS pointer resolution)

> Attackers with push permissions can read arbitrary server files via Git LFS pointer manipulation in OneDev.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2026
- **Updated:** 16 May 2026
- **Also known as:** GHSA-59wq-74xg-w85v

## What is CVE-2026-44647?

CVE-2026-44647 is a high-severity path traversal vulnerability in theonedev onedev, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OneDev is a Git server with CI/CD, kanban, and packages. Prior to 15.0.2, there is behavior that breaks the expected boundary between repository-controlled LFS metadata and server-local filesystem paths. A repository object can steer raw blob reads to arbitrary local files that the server account can access. User with push permission to any repository will be able to access any server files accessible by server process. This vulnerability is fixed in 15.0.2.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-44647?


## How do I fix CVE-2026-44647?

No fix has been published for CVE-2026-44647 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44647 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44647 and fix it if it is affected.

What it is: CVE-2026-44647 is a high-severity path traversal vulnerability in theonedev onedev, published on 14 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44647 in the wild and no public exploit code.

Affected product: theonedev onedev. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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