Skip to content
Fencer Intel
critical 9.8

CVE-2026-59774 in the critical feed json

Gitea Org-mode file disclosure and code execution

published 3mo ago modified 28d ago also EUVD-2026-101281 , GHSA-6v53-hr58-556r

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository go-gitea/gitea. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
28.3%
EPSS 28.3% chance of exploitation in 30 days, percentile 98%
public exploits
1
Metasploit

Summary

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.

Patch / fix

  • Gitea Gitea 1.27.1

Is CVE-2026-59774 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit auxiliary/gather/forgejo_orgmode_fileread_cve_2026_59774)
  2. Published

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
29d ago

Exploit prediction

28.31% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

CVSS scores

assigned by version score vector
CISA ADP 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Gitea Gitea

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of go-gitea/gitea published their own advisory on GitHub. Reviewed sources take precedence over it.