Skip to content
Fencer Intel
critical 9.8

CVE-2026-60004 kev in the critical feed json

Gitea: Remote Code Execution via diffpatch Git Hook Installation

published 2mo ago modified 2mo ago also BIT-gitea-2026-60004 , EUVD-2026-66708 , GHSA-rcr6-4jqh-j84m , GO-2026-6433

cvss
9.8
version 3.1, CNA
cisa kev
Exploited
added 2026-08-25
epss
24.0%
EPSS 24.0% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

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

Patch / fix

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.

  • go gitea.dev 1.27.1
  • bitnami gitea 1.27.1
  • Gitea Gitea 1.27.1
  • govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260916T180043-160000.1.1

suse advisories SUSE-SU-2026:23855-1SUSE-SU-2026:23863-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260916T180043-160000.1.1

opensuse advisories openSUSE-SU-2026:21897-1

  • forgejo Alpine 3.24 15.0.6-r0

alpine advisories ALPINE-CVE-2026-60004

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2026-60004 in your dependencies? 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. Added to CISA KEV
  2. Published
  3. CISA SSVC: exploitation active
  4. CISA patch deadline

Known exploited

Added
2mo ago
Patch by
2026-08-28 (2mo ago)
Ransomware
Not known
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.
Vendor, product
Gitea, Gitea
CISA name
Gitea Code Injection Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
yes
Technical impact
total
Assessed
2mo ago

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/go-gitea/gitea/security/advisories/GHSA-rcr6-4jqh-j84m referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/0xBlackash/CVE-2026-60004 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go gitea.dev
>=1.17.0, <1.27.1
<1.27.1
1.27.1
bitnami gitea
>=1.17.0, <1.27.1
1.27.1
go code.gitea.io/gitea
>=1.17.0
 no fix listed

Affected products

  • Gitea Gitea

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

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.