Gitea · Gitea · published 2026-10-06

CVE-2026-95106Gitea review and execution mismatch through duplicate tree entries

Routine No exploitation evidence; EPSS 0.3%.

CVE-2026-95106 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 27% of all CVEs. This Gitea vulnerability: CVSS 9.1 (v3.1), attacks can be automated, a successful attack gives total control of the component. Fixed upstream in Gitea 28.1.0, 28.0.0. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Gitea 28.1.0, 28.0.0.

Patch events

  1. This monthSecurity release

    DevOpsGitea

    Gitea security releases: 28.1.0, 28.0.0

    Upgrade to 28.1.028.0.0

    Why: CVE-2026-89182: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (27th pct)FIRST EPSS v2026.06.15
CVSS base score9.1 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →