# CVE-2026-119546: Forgejo through 15.0.11, 16.0.7, and 17.0.1 Path Traversal via restore-repo


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-gx58-cw96-3j3q

## What is CVE-2026-119546?

CVE-2026-119546 is a medium-severity vulnerability in forgejo, published on 30 Oct 2026. 

### Official description

Forgejo through 15.0.11, 16.0.0 through 16.0.7, and 17.0.0 through 17.0.1 contains a path traversal vulnerability in restore-repo that allows attackers to read files outside the dump directory via crafted asset paths. Attackers can supply a dump whose release.yml DownloadURL or PatchURL contains ../ sequences, importing files like app.ini as release attachments when an administrator restores it.

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

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


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

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

## Is CVE-2026-119546 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119546 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119546 is a medium-severity vulnerability in forgejo, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119546 exists.

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

## Sources

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

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