# CVE-2026-78433: Gitea private attachment disclosure through repository mismatch

> Unauthenticated attackers can access private attachments if they know the UUID, due to a missing cross-repository ownership check in Gitea.

- **Severity:** Medium 5.9 (`CVSS:3.1/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:** No
- **Published:** 14 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-frpv-2xgv-wxpq, GHSA-w7q4-4ccp-896r

## What is CVE-2026-78433?

CVE-2026-78433 is a medium-severity missing authorization vulnerability in Gitea, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gitea's web attachment handler skips its cross-repository ownership check for attachments created before 16 January 2026 and checks permissions against the repository named in the request URL instead. An unauthenticated attacker who knows a private attachment's UUID can request it through a public repository's attachment path and retrieve its contents. This can expose issue and pull request attachments or release assets; the random attachment UUID must already be known to the attacker.

Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control), CWE-1220 (Insufficient Granularity of Access Control)

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


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

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

## Is CVE-2026-78433 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78433 is a medium-severity missing authorization vulnerability in Gitea, published on 14 Oct 2026. 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-2026-78433 in the wild and no public exploit code.

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

## Sources

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

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