Skip to content
Noroxi
CVE-2026-60004· NVD / CVE Program· CNA mitre

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

Noroxi assessment

Priority: This week (action score 76/100)

  • CISA has confirmed exploitation in the wild (Aug 25, 2026). Remediation deadline for US federal agencies: Aug 28, 2026.
  • A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
  • Probability of exploitation in the next 30 days: 23.9% (FIRST EPSS); higher than 97.8% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: gitea.dev (Go) 1.27.1.

Don’t wait for the next maintenance window. Upgrade to gitea.dev (Go) 1.27.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS

CriticalCVSS 9.8 · v3.1KEVWeaponized Fix available
Published
Aug 26, 2026
Updated
Sep 8, 2026
EPSS
23.9% · 97th percentile

Report tools

JSON

Action score

76

This week

Don’t wait for the next maintenance window.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
30 / 30 · Listed
EPSS
7 / 30 · 23.9%

CISA SSVC decision

Exploitation
active
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · mitre
9.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Aug 25, 2026. That signals real attacks, not theory.

Remediation deadline for US federal agencies: Aug 28, 2026.

Get told when this record changes

  • In CISA KEV: exploitation in the wild confirmed
  • Weaponized exploit exists
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-60004

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
giteagitea

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gitea gitea1.17.0 and later · before 1.27.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.

  • Gitea Gitea

    • 1.17 and later · before 1.27.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gocode.gitea.io/giteafrom 1.17.0—
Gogitea.devfrom 1.17.0 · before 1.27.11.27.1
Gogitea.devbefore 1.27.11.27.1

Other highest-scoring records for the same primary product.

  • CVE-2020-14144The git hook feature in Gitea 1.1.0 through 1.12.5 might allow for authenticated remote code execution in customer environments where the do
    57Plan
  • CVE-2022-30781Gitea before 1.16.7 does not escape git fetch remote.
    56Plan
  • CVE-2019-11229models/repo_mirror.go in Gitea before 1.7.6 and 1.8.x before 1.8-RC3 mishandles mirror repo URL settings, leading to remote code execution.
    51Plan
  • CVE-2022-1058Open Redirect on login in go-gitea/gitea
    40Plan
  • CVE-2021-45327Gitea before 1.11.2 is affected by Trusting HTTP Permission Methods on the Server Side when referencing the vulnerable admin or user API.
    40Plan
  • CVE-2020-28991Gitea 0.9.99 through 1.12.x before 1.12.6 does not prevent a git protocol path that specifies a TCP port number and also contains newlines (
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:gitea.dev1.27.1Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×11

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Nuclei detection templateNuclei template CVE-2026-60004 —
Proof-of-concept repository on GitHubstars:52026-07-29
Proof-of-concept repository on GitHubstars:12026-07-30
Proof-of-concept repository on GitHubstars:52026-07-30
Proof-of-concept repository on GitHubstars:172026-08-03
Proof-of-concept repository on GitHubstars:02026-08-03
Proof-of-concept repository on GitHubstars:22026-08-04
Proof-of-concept repository on GitHubstars:02026-08-04
Proof-of-concept repository on GitHubstars:22026-08-08
Proof-of-concept repository on GitHubstars:12026-08-21
Proof-of-concept repository on GitHubstars:02026-08-25
Proof-of-concept repository on GitHubstars:02026-09-14

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-29 d
  2. CISA KEV-2 d
  3. Published
  4. TodayOct 16, 2026+50 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-7380049 days apartGitea reusable workflow secret exposure in pull_request_target
    0Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records