Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-60004 – Remote Code Execution – Gitea 1.17 to before 1.27.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-60004 is a critical remote code execution vulnerability in Gitea, a self-hosted Git service, caused by improper handling of patch content in the diffpatch API that allows an attacker to install a malicious Git hook. The flaw carries a CVSS v3.1 base score of 9.8 (Critical) and affects Gitea versions 1.17 through versions before 1.27.1.

Technical details

  • Root cause: In services/repository/files/patch.go, when a patch is applied twice to a bare temporary repository clone, an add/add collision occurs. Git’s three-way merge fallback extracts the indexed path even though the operation uses --cached, and because the bare clone’s root is $GIT_DIR, an attacker-controlled entry can be written to hooks/post-index-change.
  • Trigger conditions: Requires Git 2.32 or newer on the server, the diffpatch route enabled, a writable/executable temporary filesystem, and repository write access — which can be obtained via self-registration if open account registration is enabled.
  • Attack vector: Network — an attacker submits crafted patch content through the diffpatch API to plant a live Git hook that executes on subsequent index writes.
  • Impact: Arbitrary command execution as the Gitea service account, potentially exposing application secrets, database credentials, OAuth tokens, and mounted repository data.

Affected software

  • Gitea versions ≥ 1.17 and < 1.27.1

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Gitea to version 1.27.1 or later, which fixes this issue.
  • If patching is not immediately possible:
    • Disable open self-registration to prevent untrusted users from obtaining repository write access.
    • Restrict or disable the diffpatch API route where feasible.
    • Ensure the temporary filesystem used by the Gitea service is not writable/executable by untrusted processes.
    • Monitor repository and hook activity for unexpected post-index-change hook creation.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Meta tag (keywords): go,git,self-hosted,gitea
  • Raw response body: © Gitea Version:

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge