CVE-2026-60004

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-08-25), indicating real-world exploitation has been confirmed by US federal agencies. The CNA's CVSS baseline 9.8 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, the CNA's CVSS, EPSS
Exploited in the wild
9.8EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedEPSS PROB: 24%CVSS: 9.8Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/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.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (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 available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
24%
EPSS %ILE
97th
KEV
⚠ Exploited

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

A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.

Exploitation active (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 & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

In CISA KEV yes (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

CISA required action“Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://github.com/go-gitea/gitea/security/advisories/GHSA-rcr6-4jqh-j84m · https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk · https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk · https://nvd.nist.gov/vuln/detail/CVE-2026-60004

Published

August 26, 2026

Last Modified

September 8, 2026

Advisory Details (5)

Auto-updated Oct 14, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: github.
Web page

GitHub - 0xBlackash/CVE-2026-60004: CVE-2026-60004 · GitHub

https://github.com/0xBlackash/CVE-2026-60004
Web page

Gitea vulnerability CVE-2026-60004: find impacted assets

https://www.runzero.com/blog/gitea/
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Remote Code Execution via diffpatch Git Hook Installation · Advisory · go-gitea/gitea · GitHub

https://github.com/go-gitea/gitea/security/advisories/GHSA-rcr6-4jqh-j84m
Web page

Gitea 1.27.1 is released | Gitea Blog

https://blog.gitea.com/release-of-1.27.1/
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-60004

Vendor Advisories for CVE-2026-60004(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
code.gitea.io/gitea—
  • 1.17.0 on: no fix on record
—
gitea.dev—
  • 1.17.0 up to 1.27.1: fixed in 1.27.1
  • every version up to 1.27.1: fixed in 1.27.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 55× 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-14 09:42 UTCEG score recompute
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 24% · 97th percentile
  3. 2026-10-13 07:54 UTCEG score recompute
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 24% · 97th percentile
  5. 2026-10-12 15:52 UTCEG score recompute
  6. 2026-10-11 19:36 UTCEG score recompute
  7. 2026-10-11 16:51 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 24% · 97th percentile
  9. 2026-10-11 13:41 UTCEG score recompute
  10. 2026-10-10 21:15 UTCEG score recompute
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 24% · 97th percentile
  12. 2026-10-09 20:35 UTCEG score recompute
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 24% · 97th percentile
  14. 2026-10-08 20:01 UTCEG score recompute
  15. 2026-10-08 17:13 UTCEPSS rescoreEPSS 24% · 97th percentile
  16. 2026-10-08 03:34 UTCEG score recompute
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 24% · 97th percentile
  18. 2026-10-06 18:47 UTCEG score recompute
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 24% · 97th percentile
  20. 2026-10-05 18:11 UTCEG score recompute
  21. 2026-10-05 17:43 UTCEPSS rescoreEPSS 24% · 97th percentile
  22. 2026-10-03 17:00 UTCEG score recompute
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 24% · 97th percentile
  24. 2026-10-02 20:31 UTCEG score recompute
  25. 2026-10-02 17:56 UTCEPSS rescoreEPSS 24% · 97th percentile
Show 64 more
  1. 2026-10-01 19:56 UTCEG score recompute
  2. 2026-10-01 19:50 UTCEPSS rescoreEPSS 24% · 97th percentile
  3. 2026-09-30 15:12 UTCEG score recompute
  4. 2026-09-30 15:03 UTCEPSS rescoreEPSS 24% · 97th percentile
  5. 2026-09-29 18:41 UTCEG score recompute
  6. 2026-09-28 22:12 UTCEG score recompute
  7. 2026-09-28 13:57 UTCEG score recompute
  8. 2026-09-28 13:51 UTCEPSS rescoreEPSS 24% · 97th percentile
  9. 2026-09-27 21:51 UTCCISA KEV update
  10. 2026-09-27 17:27 UTCEG score recompute
  11. 2026-09-26 16:53 UTCEG score recompute
  12. 2026-09-26 15:59 UTCEPSS rescoreEPSS 24% · 97th percentile
  13. 2026-09-26 04:36 UTCEG score recompute
  14. 2026-09-25 19:35 UTCCISA KEV update
  15. 2026-09-25 14:55 UTCCISA KEV update
  16. 2026-09-24 19:31 UTCCISA KEV update
  17. 2026-09-24 15:40 UTCEG score recompute
  18. 2026-09-22 19:36 UTCCISA KEV update
  19. 2026-09-22 18:35 UTCEG score recompute
  20. 2026-09-21 22:07 UTCEG score recompute
  21. 2026-09-21 19:09 UTCCISA KEV update
  22. 2026-09-19 16:50 UTCEG score recompute
  23. 2026-09-18 20:21 UTCEG score recompute
  24. 2026-09-18 19:28 UTCEPSS rescoreEPSS 87% · 99th percentile
  25. 2026-09-18 19:20 UTCCISA KEV update
  26. 2026-09-18 14:15 UTCCISA KEV update
  27. 2026-09-16 15:03 UTCEG score recompute
  28. 2026-09-16 14:10 UTCCISA KEV update
  29. 2026-09-16 14:08 UTCEPSS rescoreEPSS 87% · 99th percentile
  30. 2026-09-14 19:24 UTCCISA KEV update
  31. 2026-09-12 16:48 UTCEG score recompute
  32. 2026-09-11 18:49 UTCCISA KEV update
  33. 2026-09-10 19:28 UTCCISA KEV update
  34. 2026-09-10 11:33 UTCEG score recompute
  35. 2026-09-10 09:35 UTCEPSS rescoreEPSS 87% · 99th percentile
  36. 2026-09-09 19:08 UTCCISA KEV update
  37. 2026-09-08 18:54 UTCCISA KEV update
  38. 2026-09-08 18:32 UTCEG score recompute
  39. 2026-09-07 18:53 UTCEG score recompute
  40. 2026-09-07 16:01 UTCEPSS rescoreEPSS 87% · 99th percentile
  41. 2026-09-06 14:07 UTCEG score recompute
  42. 2026-09-06 13:47 UTCEPSS rescoreEPSS 87% · 99th percentile
  43. 2026-09-05 17:39 UTCEG score recompute
  44. 2026-09-04 17:38 UTCCISA KEV update
  45. 2026-09-04 17:00 UTCEG score recompute
  46. 2026-09-04 08:46 UTCEG score recompute
  47. 2026-09-04 05:07 UTCEPSS rescoreEPSS 87% · 99th percentile
  48. 2026-09-02 17:33 UTCCISA KEV update
  49. 2026-09-01 15:02 UTCEG score recompute
  50. 2026-09-01 13:54 UTCEPSS rescoreEPSS 87% · 99th percentile
  51. 2026-08-31 14:19 UTCCISA KEV update
  52. 2026-08-30 21:55 UTCEG score recompute
  53. 2026-08-30 19:17 UTCEPSS rescoreEPSS 85% · 99th percentile
  54. 2026-08-29 00:47 UTCEG score recompute
  55. 2026-08-28 21:42 UTCEPSS rescoreEPSS 85% · 99th percentile
  56. 2026-08-27 20:02 UTCEG score recompute
  57. 2026-08-27 17:22 UTCCISA KEV update
  58. 2026-08-27 15:56 UTCEG score recompute
  59. 2026-08-27 14:25 UTCEPSS rescoreEPSS 82% · 99th percentile
  60. 2026-08-27 11:49 UTCEG score recompute
  61. 2026-08-26 23:10 UTCEG score recompute
  62. 2026-08-26 20:26 UTCEG score recompute
  63. 2026-08-26 20:07 UTCEG score recomputeFirst assessed: 9.8 CRITICAL
  64. 2026-08-26 20:06 UTCMITRE cvelistV5first tracked

Publicly available exploits

(6 references)

Public exploit code is referenced for this CVE (5 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • GitHub PoCgagaltotal/CVE-2026-60004-poc-gitea
    Published Aug 8, 2026

    CVE-2026-60004 — Gitea Pre-Auth RCE via diffpatch hook injection

    Open source ↗
  • GitHub PoCHackSpeak/CVE-2026-60004
    Published Aug 4, 2026

    Gitea diffpatch RCE (CVE-2026-60004) PoC - repo-write to RCE as Gitea service account

    Open source ↗
  • GitHub PoCimbas007/CVE-2026-60004-POC
    Published Aug 3, 2026

    CVE-2026-60004 Pre-Auth RCE Exploit — Gitea <= 1.27.0 diffpatch git hook injection (CVSS 9.8)

    Open source ↗
  • Nucleihttp/cves/2026/CVE-2026-60004.yaml
    Published Aug 3, 2026

    Gitea <= 1.27.0 - Pre-Auth Remote Code Execution

    Open source ↗
  • GitHub PoC0xBlackash/CVE-2026-60004
    Published Jul 30, 2026

    CVE-2026-60004

    Open source ↗
  • GitHub PoCHORKimhab/CVE-2026-60004
    Published Jul 29, 2026

    CVE-2026-60004

    Open source ↗

Frequently asked(6)

What is CVE-2026-60004?
CVE-2026-60004 is a critical-severity vulnerability; its CVE record was published on August 26, 2026. Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.
When was the CVE record for CVE-2026-60004 published?
The CVE record for CVE-2026-60004 was published on August 26, 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 September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-60004 actively exploited?
Yes. CISA added CVE-2026-60004 to the Known Exploited Vulnerabilities catalog on August 25, 2026, affecting Gitea Gitea. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2026-60004?
CVE-2026-60004 has a CVSS base score of 9.8 (the CNA's own assessment, by mitre; NVD's own analysis pending).
Which products are affected by CVE-2026-60004?
CVE-2026-60004 affects Gitea Gitea. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2026-60004?
A fix for CVE-2026-60004 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-60004 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-60004

Explore →

Is Your Infrastructure Affected by CVE-2026-60004?

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