Unknown severity · Source severity not reportedCVE-2026-125423

Gitea command execution through repository auto-initializationCVE-2026-125423

Answer in brief

CVE-2026-125423 records a Unknown severity vulnerability in Gitea command execution through repository auto-initialization. The current sources do not mark it as known exploited. The current feed maps Gitea/Gitea (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Nov 15, 2026Updated Nov 15, 2026Source checked Nov 15, 2026First seen by HOL Nov 15, 2026Material review Nov 15, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Gitea/Gitea (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Gitea/Giteageneric	>=0 <28.4.0	28.4.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for Gitea/Gitea.
Review the reported fix. Update Gitea/Gitea to 28.4.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Nov 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Nov 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Nov 15, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.