# CVE-2026-59774: Gitea Org-mode file disclosure and code execution

> Unauthenticated attackers can read server files via Org-mode INCLUDE directives and potentially execute code by chaining with token disclosure.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 15 Oct 2026
- **Also known as:** GHSA-6v53-hr58-556r

## What is CVE-2026-59774?

CVE-2026-59774 is a critical path traversal 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 Org-mode markup renderer processes INCLUDE directives supplied to the repository markup endpoint without preventing access to server-side files. An unauthenticated attacker can use a suitable public repository to read files accessible to the Gitea service account. If the disclosed files include app.ini and its INTERNAL_TOKEN, the attacker can chain the disclosure with internal logger access to modify a Git hook and execute commands as the Gitea service account.

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

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


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

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

## Is CVE-2026-59774 being exploited?

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

Public exploit code:

- CVE-2026-59774 (github_poc): https://github.com/FlowerWitch/CVE-2026-59774_docker
- PoC for Gitea versions before 1.27.1 is vulnerable to Path Traversal (CWE-22), which leads to unauthenticated arbitrary file read / information disclosure leading to RCE CVSS 9.8 (github_poc): https://github.com/asvorg/CVE-2026-59774-poc
- Gitea LFI to RCE exploit (CVE-2026-59774) — arbitrary file read via Org-mode #+INCLUDE, chained to remote code execution through git hook injection (github_poc): https://github.com/Ly0kha/CVE-2026-59774
- Forgejo Arbitrary File Read via Org-mode Include (metasploit)
- Gitea 1.22.1-1.27.0 - Unauthenticated Arbitrary File Read (nuclei): http/cves/2026/CVE-2026-59774.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59774 is a critical path traversal 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59774 exists.

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

## Sources

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

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