CVE-2026-59774

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 28% (98th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS
Trending — 4 sources updated this weekWeaponized
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit code is available (Metasploit, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 28%CVSS: 9.8Exploit: Metasploit · other public PoCExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
85
EG Risk 85/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
28%
EPSS %ILE
98th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 14, 2026

Last Modified

October 15, 2026

Advisory Details (5)

Auto-updated Oct 15, 2026
Fix referenced — no release confirmed yet. Sources: github_pr, github.
Web page

oss-security - CVE-2026-59774: Arbitrary file read via the Org-mode #+INCLUDE directive in Gitea and Forgejo

http://www.openwall.com/lists/oss-security/2026/08/10/3
GitHub advisoryMentions a patch (unverified)

Unauthenticated Arbitrary File Read can lead to RCE · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-6v53-hr58-556r
GitHub pull request

fix: orgmode render include path (#38642)

Fix merged in go-gitea/gitea PR #38645 on 2026-07-26 — awaiting tagged release

https://github.com/go-gitea/gitea/pull/38645
GitHub pull request

fix: orgmode render include path

Fix merged in go-gitea/gitea PR #38642 on 2026-07-26 — awaiting tagged release

https://github.com/go-gitea/gitea/pull/38642
Web page

Gitea 1.27.1 is released | Gitea Blog

https://blog.gitea.com/release-of-1.27.1/

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-16 16:43 UTCEPSS rescoreEPSS 28% · 98th percentile
  2. 2026-10-16 05:54 UTCEG score recompute
  3. 2026-10-15 16:32 UTCEPSS rescoreEPSS 28% · 98th percentile
  4. 2026-10-15 04:01 UTCEG score recompute
  5. 2026-10-14 16:30 UTCEG score recomputeFirst assessed: 9.8 CRITICAL
  6. 2026-10-14 16:25 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  7. 2026-10-14 15:25 UTCNVD update
  8. 2026-10-14 14:42 UTCEG score recompute
  9. 2026-10-14 14:39 UTCMITRE cvelistV5first tracked

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 GitHub PoC), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. No release with the fix is confirmed, so defenders should restrict or isolate affected systems accordingly until one is applied.

  • Metasploitauxiliary/gather/forgejo_orgmode_fileread_cve_2026_59774✓ verified
    Published Aug 21, 2026

    Forgejo Arbitrary File Read via Org-mode Include

    Open source ↗
  • Nucleihttp/cves/2026/CVE-2026-59774.yaml
    Published Aug 13, 2026

    Gitea 1.22.1-1.27.0 - Unauthenticated Arbitrary File Read

    Open source ↗
  • GitHub PoCFlowerWitch/CVE-2026-59774_docker
    Published Aug 6, 2026

    CVE-2026-59774

    Open source ↗

Frequently asked(5)

What is CVE-2026-59774?
CVE-2026-59774 is a critical-severity vulnerability; its CVE record was published on October 14, 2026. 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…
When was the CVE record for CVE-2026-59774 published?
The CVE record for CVE-2026-59774 was published on October 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2026-59774 actively exploited?
CVE-2026-59774 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 28% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59774?
CVE-2026-59774 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-59774?
A fix for CVE-2026-59774 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-59774

Explore →

Is Your Infrastructure Affected by CVE-2026-59774?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.