Skip to main content
Menu
CVEs

CVE

Gitea command execution via repository auto-initialization

Affects Gitea versions before 28.4.0 on servers where repositories are created with auto_init=true using the Default README template. Fixed in 28.4.0.

CVE-2026-125423EUVD-2026-126115

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

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

8.8HighCISA-ADP
Exploited
No known exploitation
Fix
Fixed in 28.4.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Gitea repository created with auto_init=true using the Default README template Attacker's pushed ref must become visible before the clone/checkout for initial commit generation (timing race) Server-side Git symlink support is available

Published
Last modified
Reference
Last checked
0.13% · 2nd percentile
18/100 · provisional
Specific setups only
1 proof of concept on GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

Gitea versions affected by this bug let a user who is allowed to create repositories run commands as the Gitea system user. The flaw is in repository auto-initialization: a push sent before setup finishes can use a symbolic link to overwrite a server-side git hook.

Original description

A repository created with auto-init accepted pushes before its initialization had finished, and the initial commit was built in a checkout of whatever the repository already contained. A user who is allowed to create repositories could push a crafted tree during that window so that writing the README followed a symbolic link and overwrote a server-side git hook, which runs commands as the Gitea system user. The initial commit is now built in a freshly initialized directory, and a new repository only becomes ready, and accepts pushes, once its initialization is complete.

cve.now Index

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.8/10CVSS 8.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 25 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Gitea repository created with auto_init=true using the Default README template Attacker's pushed ref must become visible before the clone/checkout for initial commit generation (timing race) Server-side Git symlink support is available
  • Upgrade to a fixed version: 28.4.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-125423 (Gitea command execution through repository auto-initialization), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125423 (entry last updated 2026-11-16):
Affected:
- Gitea Gitea: fixed in 28.4.0
Fixed versions: 28.4.0.
Conditions (all must be true for the bug to be hit):
- Gitea repository created with auto_init=true using the Default README template (source: https://github.com/go-gitea/gitea/security/advisories/GHSA-6m4f-m9vc-7946)
- Attacker's pushed ref must become visible before the clone/checkout for initial commit generation (timing race) (source: https://github.com/go-gitea/gitea/security/advisories/GHSA-6m4f-m9vc-7946)
- Server-side Git symlink support is available (source: https://github.com/go-gitea/gitea/security/advisories/GHSA-6m4f-m9vc-7946)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-125423 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125423 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/go-gitea/gitea/security/advisories/GHSA-6m4f-m9vc-7946
- https://github.com/go-gitea/gitea/pull/40376
- https://github.com/go-gitea/gitea/pull/40383
- https://blog.gitea.com/release-of-28.4.0/
- https://github.com/go-gitea/gitea/releases/tag/v28.4.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125423
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125423"}.

Public exploit activity

10Nov 15Nov 17
  • GitHub PoC repos: 1

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Timeline

  1. CVE published
  2. First seen by cve.now1 day
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • gitea.dev

    fixed in 28.4.0

Evidence 8

Vendor advisory · 2

Establishes: Affected and fixed versions.

  1. Advisory
  2. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Public exploit code · 1

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

  1. Exploit

Other links · 3

  1. Patch
  2. Patch
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-125423

Is CVE-2026-125423 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Creating a repository with auto-initialization and the Default README template can let a pushed ref interfere with initial commit generation. A symlinked README.md can then overwrite a server-side Git hook, which runs commands as the operating-system account that runs Gitea.Source: github.com, blog.gitea.com

Which versions are affected by CVE-2026-125423?

gitea.dev: before 28.4.0.Source: cve.now feed data

Am I affected, and how do I check?

Gitea versions before 28.4.0 are affected. The setup also requires repositories created with auto_init=true using the Default README template, on a server with Git symlink support. To check, confirm the installed Gitea version and whether auto-initialization with the Default README template is used.Source: github.com, blog.gitea.com

How do I fix CVE-2026-125423?

Upgrade Gitea to version 28.4.0 or later, which contains the fix.Source: github.com, blog.gitea.com