Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCreate/push repo with malicious .org file
-
ExploitCraft #+INCLUDE path-traversal directive
-
ExecutionTrigger server-side org-mode rendering
-
ImpactDisclose arbitrary server files
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that Gitea render an attacker-controlled Org-mode ( |
| Impact | The input assigns CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), which rates this as critical network-exploitable with full CIA impact and no privileges. However, the GitHub PR diff (go-gitea/gitea#38642) shows the actual flaw is in org-mode markup rendering: the parser honored |
| Exploit ScenarioDerived | An attacker creates or pushes a repository to a Gitea instance containing a crafted Org-mode ( |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 14, 2026
Path traversal in Gitea's Org-mode (.org) markup renderer allows an attacker who can get Org-mode content rendered by the server to read arbitrary files from the Gitea host filesystem, through abuse of the #+INCLUDE: directive. Affected releases are Gitea 1.22 through versions prior to 1.27.1 (including the Alpine Linux gitea package, fixed in 1.27.1-r0); publicly available exploit code exists, and vendor patches are available. The input's 9.8 CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) overstates the issue relative to our independent assessment (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), which characterizes this as an authenticated arbitrary file disclosure rather than unauthenticated remote code execution with full integrity and availability impact. No CISA KEV entry was provided, so active exploitation is not confirmed.
Earlier versions of this analysis (1)
Gitea received a security fix in Alpine Linux package version 1.27.1-r0, addressing an unspecified vulnerability tracked as CVE-2026-59774. The underlying vulnerability class, attack vector, and impact are not disclosed in the available intelligence. Administrators running Gitea on Alpine Linux should treat this as an uncharacterized security fix and upgrade promptly, as the absence of public detail does not imply low severity.
RemediationAI
Upgrade to Gitea 1.27.1 or later - the vendor-released patch is version 1.27.1, and Alpine Linux users should move to the gitea 1.27.1-r0 package from the Alpine repositories (see the upstream security advisory at https://github.com/go-gitea/gitea/security/advisories/GHSA-6v53-hr58-556r, the release notes at https://github.com/go-gitea/gitea/releases/tag/v1.27.1, and the blog post at https://blog.gitea.com/release-of-1.27.1/ for the exact version). Operators who cannot upgrade immediately should backport the fix from https://github.com/go-gitea/gitea/pull/38642 (and the companion change at https://github.com/go-gitea/gitea/pull/38645), which replaces the Org-mode file reader with a no-op that renders #+INCLUDE: directives as plain text - the trade-off being that legitimate cross-file Org-mode includes are no longer resolved and will display literally. Where patching is not feasible, mitigating options include disabling Org-mode rendering for untrusted content (for example, restricting which file extensions the markup pipeline processes, or turning off the org-mode renderer entirely), which removes the attack surface but degrades wiki/repository documentation rendering, and tightening content-creation privileges so that only trusted accounts can push or post content that the server will render, along with running the Gitea process under a restricted service account and filesystem confinement (read-only mounts, SELinux/AppArmor profiles) to limit what a successful traversal could disclose. Because public exploit code is already available, patching should be treated as time-sensitive.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw resides in Gitea's Org-mode markup module (modules/markup/orgmode/orgmode.go), which wraps the Go go-org parsing library to render Org-mode documents in repositories, wikis, issues, and comments. Org-mode supports a #+INCLUDE: directive that instructs the parser to fetch and inline the contents of another file; by default the library resolves such paths on the local filesystem via its ReadFile hook. Because Gitea passed attacker-supplied document content straight into org.New().Silent().Parse(...) without constraining that file access, a crafted #+INCLUDE: path could traverse outside any intended render root and disclose server-side files - the classic CWE-22 (Improper Limitation of a Pathname to a Restricted Directory / Path Traversal) pattern applied to a file-inclusion feature. The upstream fix referenced by PR 38642 replaces the default reader with a stub cfg.ReadFile that never touches disk, instead emitting the literal text #+INCLUDE: [[<path>]] so that the directive degrades to plain text rather than performing any I/O; a companion change (PR 38645) and test coverage (TestRender_IncludeLink) accompany it. Exploitation therefore hinges on the orgmode renderer being reached with attacker-controlled .org content, and the practical impact is arbitrary file read (confidentiality), not command execution.
Know when Gitea gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attacker must host a malicious .org file, typically requiring an account (PR:L); the INCLUDE flaw yields arbitrary file disclosure (C:H) with no integrity or availability impact (I:N/A:N).
Primary rating from Vendor (vendor:alpine).
CVSS VectorVendor: vendor:alpine
Lifecycle Timeline
2DescriptionCVE.org
Alpine Linux: gitea fixed in 1.27.1-r0
Executive ViewAI
Gitea - the self-hosted source code and CI platform used across our engineering organization - has a critical-severity flaw in its Org-mode markup renderer that lets an attacker read arbitrary files from the server hosting the instance, including configuration files that hold database credentials, API tokens, and signing keys. Public exploit code is already circulating, so any Gitea instance we run between versions 1.22 and 1.27.1 (including the Alpine gitea package) should be treated as a likely near-term target. Leadership should care because a single successful read can expose the secrets that protect our entire code repository and build pipeline, turning a code-hosting compromise into a broader credential and intellectual-property incident.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Remote code execution in Gitea (self-hosted Git service) via a code-injection flaw (CWE-94) allows attackers to run arbi
Broken access control in Gitea's Composer package registry (versions up to and including 1.26.1) lets remote attackers r
Gitea before 1.16.7 does not escape git fetch remote. Rated high severity (CVSS 7.5), this vulnerability is remotely exp
The git hook feature in Gitea 1.1.0 through 1.12.5 might allow for authenticated remote code execution in customer envir
Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Gitea Gitea
Reverse-proxy authentication bypass in the official Gitea Docker image (versions up to and including 1.26.2) allows any
Container escape in Gitea act_runner (Docker backend, through act 0.262.0) lets an authenticated user with workflow-exec
models/repo_mirror.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 mishandles mirror repo URL settings, leading to rem
Server-side request forgery and internal repository exfiltration in Gitea before 1.27.0 lets a low-privileged authentica
Authorization bypass in Gitea versions 1.22.3 through 1.26.1 allows holders of `public-only` access tokens or OAuth gran
An issue was discovered in Gitea through 1.11.5. Rated high severity (CVSS 7.5), this vulnerability is remotely exploita
Missing Authorization in GitHub repository go-gitea/gitea prior to 1.16.4. Rated high severity (CVSS 7.1), this vulnerab
EUVD-2026-101281
NVD
CVE.org
EPSS
GitHub
Exploit-DB