BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-60004High confidence

Gitea Code Injection Vulnerability

Gitea · Gitea

Official source article: GitHub GHSA-RCR6-4JQH-J84M ↗. Check the applicable product and release in the original source.

9.8CriticalCVSS 3.1
Recommended action
Mitigate now

CISA confirms exploitation in the wild and lists 2026-08-28 as the remediation due date.

Mitigation available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • CISA confirms exploitation in the wild.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 23.99% for the current model date.

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Gitea Gitea and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges4 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gocode.gitea.io/giteaSEMVER: introduced 1.17.0Not statedOSV record ↗aggregator derived · 10 Sep 2026
Gogitea.devSEMVER: introduced 1.17.0; fixed 1.27.11.27.1OSV record ↗aggregator derived · 10 Sep 2026
Gogitea.devSEMVER: introduced 0; fixed 1.27.11.27.1OSV record ↗aggregator derived · 10 Sep 2026
gogitea.dev>= 1.17.0, < 1.27.11.27.1GitHub advisory ↗upstream repository advisory · 8 Sep 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-66708

CISA KEV mirrored by ENISA

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

EUVD state
Present in the current official mapping
Known exploitation
Recorded by ENISA since 25 Aug 2026. Evidence sources: cisa_kev.
ENISA score
9.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionMitigate now

CISA confirms exploitation in the wild and lists 2026-08-28 as the remediation due date.

Mitigation available
01

What, why and how

Gitea contains a code injection vulnerability that allows an attacker with repository write access to send a malicious patch to the diffpatch API endpoint to plant an executable Git hook and run shell commands as the Gitea service account.

What

Gitea contains a code injection vulnerability that allows an attacker with repository write access to send a malicious patch to the diffpatch API endpoint to plant an executable Git hook and run shell commands as the Gitea service account.

Why

Untrusted data can cross into a code-evaluation path and be interpreted as executable instructions.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Gitea contains a code injection vulnerability that allows an attacker with repository write access to send a malicious patch to the diffpatch API endpoint to plant an executable Git hook and run shell commands as the Gitea service account.

Why

Untrusted data can cross into a code-evaluation path and be interpreted as executable instructions.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Confirmed in the wild

CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2026-08-25.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improper Control of Generation of Code ('Code Injection') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-94 ↗

CWE-94: Improper Control of Generation of Code ('Code Injection'). The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-94CISA KEVPublic exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-66708Known-exploited evidence recorded

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

Official EUVD record ↗
BSI · German · WID-SEC-2026-2557Gitea: Schwachstelle ermöglicht Codeausführung

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Gitea ausnutzen, um beliebigen Programmcode auszuführen.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV26-845Gitea security advisory (AV26-845) - Update 1

As of August 14, 2026, Gitea is affected by vulnerabilities in the following product: Update 1 Open-source reporting indicates that CVE-2026-20896 is being exploited in the wild.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260902Security Bulletin 2 Sept 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 2 Sept 2026, published on 2 September 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CSIRT Italia · Italian · rilevato-sfruttamento-di-vulnerabilita-in-giteaRilevato sfruttamento di vulnerabilità in Gitea

La vulnerabilità - identificata tramite la CVE-2026-60004, di tipo "Code Injection" e con score CVSS v3.1 pari a 9.8 - interessa il componente responsabile dell'applicazione delle patch nell'endpoint diffpatch ed è causata da un'errata gestione dei repository temporanei utilizzati durante l'elaborazione delle patch. In particolari condizioni, un utente remoto malintenzionato può sfruttare il meccanismo dei Git Hook per scrivere ed eseguire codice arbitrario all'interno della directory del repository temporaneo tramite una patch opportunamente costruita. Durante le successive operazioni Git, il codice malevolo viene eseguito automaticamente con i privilegi dell'utente di sistema che esegue il servizio Gitea.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-030789gitea projectのgiteaにおけるコードインジェクションの脆弱性

Gitea 1.27.1 より前のバージョンでは、Git フックのインストールを通じて diffpatch API 経由でリモートコード実行が可能となっています。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6957Gitea 제품 보안 업데이트 권고

Gitea에서 발생하는 Code Injection 취약점(CVE-2026-60004) [1][2]

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6929Gitea 제품 보안 업데이트 권고

Gitea에서 발생하는 Code Injection 취약점(CVE-2026-60004) [1][2]

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6927美 CISA 발표 주요 Exploit 정보공유(Update. 2026-08-25)

Gitea Code Injection Vulnerability

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Mitigation available
Affected
Gitea: 1.17 < 1.27.1
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Apply the mitigation in the linked authoritative guidance while planning the vendor's permanent fix.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
Official vendor articles1 stored document

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

04

Evidence and provenance

Published 26 Aug 2026 · Last source change 8 Sept 2026, 18:03 UTC · CWE-94 · Improper Control of Generation of Code ('Code Injection')

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-27
European sourceENISA EUVD · EUVD-2026-66708
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    1.17 < 1.27.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    Gitea: 1.17 < 1.27.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  2. ENISA known-exploited stateENISA EUVD now records this CVE in its known-exploited dataset.
    Before
    not listed in ENISA EUVD known-exploited dataset
    After
    listed in ENISA EUVD known-exploited dataset (EUVD-2026-66708)
    ENISA EUVD ↗
  3. ENISA EUVD mappingEUVD-2026-66708 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2026-66708"}
    ENISA EUVD ↗
  4. Vendor guidanceAuthoritative vendor guidance changed: added mitigation: github.com/CVE-2026-60004; added remediation: github.com/CVE-2026-60004; 1 further additions.
    Before
    no authoritative guidance recorded
    After
    mitigation: github.com/CVE-2026-60004 · remediation: github.com/CVE-2026-60004 · vendor advisory: github.com/GHSA-rcr6-4jqh-j84m
    cve@mitre.org ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    cve@mitre.org ↗
  6. Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.
    Before
    No public exploit
    After
    Public exploit reference
    cve@mitre.org ↗
  7. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Added to CISA KEV
Mitigation reference recorded
ENISA EUVD · EUVD-2026-66708↗CISA KEV record↗Public exploit reference · GitHub GHSA-RCR6-4JQH-J84M↗Public exploit reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-60004 · cve.blacktree.nl