CVE-2026-95106

Gitea review and execution mismatch through duplicate tree entries

Published Oct 6, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
Gitea accepted pushed Git trees containing two entries with the same name, which Git's own consistency checks reject. Gitea's web views resolved such a path to the first entry, while `git checkout`, Gitea Actions, and release archives use the last. A contributor could open a pull request whose diff and file views show benign content while CI and checkouts at the same commit use different, attacker-controlled content. Incoming objects are now checked for consistency; objects already stored in existing repositories are not rescanned.

Analysis

AI-generated

Technical impact

A vulnerability exists where Gitea accepts pushed Git trees containing duplicate entries with identical names. Git itself rejects such objects, but Gitea's internal logic does not enforce consistency for existing repositories. This mismatch enables the web interface to display one version of a file while tools such as git checkout, Actions, and release archives provide a different, attacker-controlled version. The condition permits malicious content to be introduced into CI pipelines or release artifacts, effectively enabling remote code execution in environments that consume the repository.

Affected Systems

The affected products are Gitea repositories hosted on instances running versions prior to 28.0.0.0 and later add consistency checks for incoming objects. This includes any users who host projects on those instances and have the ability to push or create pull requests. The exact affected versions cannot be enumerated from the data, but the fix was introduced in 28.0.0, implying that earlier releases are impacted.

Risk and Exploitability

The vulnerability is exploitable over any interface that accepts pushes, such as HTTP or SSH, and the attack vector is inferred to be a normal Git push or pull request. The EPSS score indicates < 1% probability of exploitation, and the vulnerability is not listed in CISA's KEV, so no widespread exploitation has been reported. Nonetheless, the description indicates the potential for code execution and push-based exploitation, but due to lack of official metrics, the likelihood and overall risk level cannot be precisely quantified. The CVSS base score of 9.1 indicates high severity.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Gitea to version 28.0.0 or later, which adds consistency checks for incoming objects
  • Rescan existing repositories or recreate affected ones to ensure no duplicate entries exist
  • Avoid pushing repositories that contain duplicate file names until the issue is resolved, or apply temporary manual inspections of incoming trees

Generated by OpenCVE AI on October 7, 2026 at 23:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Weaknesses CWE-706
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Gitea
Gitea gitea
Vendors & Products Gitea
Gitea gitea
Type Values Removed Values Added
Weaknesses CWE-200
CWE-281
CWE-287
Type Values Removed Values Added
Description Gitea accepted pushed Git trees containing two entries with the same name, which Git's own consistency checks reject. Gitea's web views resolved such a path to the first entry, while `git checkout`, Gitea Actions, and release archives use the last. A contributor could open a pull request whose diff and file views show benign content while CI and checkouts at the same commit use different, attacker-controlled content. Incoming objects are now checked for consistency; objects already stored in existing repositories are not rescanned.
Title Gitea review and execution mismatch through duplicate tree entries
References
Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-281

    Improper Preservation of Permissions

  • CWE-287

    Improper Authentication

  • CWE-706

    Use of Incorrectly-Resolved Name or Reference

Sources

Status
PUBLISHED
Assigner
Gitea
Published
Updated
Oct 7, 2026, 8:08 PM
Reserved
Oct 4, 2026, 9:57 PM
Status
Analyzed
Published
Oct 6, 2026, 8:17 PM
Modified
Oct 13, 2026, 4:27 PM