Gitea Org-mode file disclosure and code execution
What fixes it
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Timeline
- 30 Jul 2026Exploit code publicMetasploit
- 14 Oct 2026, 14:28 UTCPublishedCVE List
Public exploit code and templates 2
- Auxiliary moduleForgejo Arbitrary File Read via Org-mode Include 30 Jul 2026Metasploit
- Scanner templateGitea 1.22.1-1.27.0 - Unauthenticated Arbitrary File ReadNuclei
Listed so defenders can prioritize. Threatline links to the source and does not host exploit code.
Reports 1
1 outlet mention it. Reports are not confirmation; each links to its source.
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.
Text from CVE List
Affected versions 2
- Giteaaffected: 1.22 before 1.27.1CVE List
- gitea.dev, go1.22 < 1.27.1GitHub
References 5
- github.com/go-gitea/gitea/pull/38642Fixvia CVE List
- github.com/go-gitea/gitea/pull/38645Fixvia CVE List
- github.com/go-gitea/gitea/releases/tag/v1.27.1Fixvia CVE List
- github.com/go-gitea/gitea/security/advisories/GHSA-6v53-hr58-556rAdvisoryvia CVE List
- blog.gitea.com/release-of-1.27.1/Referencevia CVE List