Skip to main content
VulnerabilityPublished Updated

CVE-2026-20912: Gitea Open Source Git Server · Improper Access Control

Affects Gitea Open Source Git ServerSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GiteaGitea Open Source Git ServerAffected
  • <=1.25.3
Fixed in–

AI-suggested

Users should monitor the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-20912 for updates on patches or official mitigations. Until a fix is available, restrict repository release attachment operations to trusted users and review repository permissions carefully to minimize exposure risk.

Description

Gitea does not properly validate repository ownership when linking attachments to releases. An attachment uploaded to a private repository could potentially be linked to a release in a different public repository, making it accessible to unauthorized users.

References

Community reviews

Loading reviews…