CVE-2026-95106 Affecting gitea package, versions <28.0.0-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.29% (20th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-GITEA-20942357
  • published15 Oct 2026
  • disclosed6 Oct 2026

Introduced: 6 Oct 2026

NewCVE-2026-95106  (opens in a new tab)

How to fix?

Upgrade Minimos:latest gitea to version 28.0.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream gitea package and not the gitea package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

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.