Skip to content
Fencer Vulns
medium 6.5

CVE-2026-20800 json

Notification API Leaks Private Repository Issue Titles After Collaborator Permission Revocation

published 2026-01-22 9 mo ago modified 2026-09-08 2 mo ago also BIT-gitea-2026-20800 , EUVD-2026-4268 , GHSA-2vgv-hgv4-22mh , GHSA-g54m-9f6g-wj7q , GO-2026-4362

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

Gitea's notification API does not re-validate repository access permissions when returning notification details. After a user's access to a private repository is revoked, they may still view issue and pull request titles through previously received notifications.

Patch / fix

  • go github.com/go-gitea/gitea 1.25.4
  • bitnami gitea 1.25.4
  • go code.gitea.io/gitea 1.25.4
  • gitea gitea 1.25.4
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20260205T172317-150000.1.146.1

suse advisories SUSE-SU-2026:0403-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
9 mo ago

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/go-gitea/gitea
<1.25.4
1.25.4
bitnami gitea
<1.25.4
1.25.4
go code.gitea.io/gitea
<1.25.4
1.25.4

Affected products

  • Gitea Gitea Open Source Git Server

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.