Skip to content
Fencer Intel
medium 6.5

CVE-2026-20883 json

Gitea Stopwatch API Missing Authorization Check Leads to Post-Revocation Information Disclosure

published 9mo ago modified 2mo ago also BIT-gitea-2026-20883 , EUVD-2026-4267 , GHSA-644v-xv3j-xgqg , GHSA-j8xr-c56q-m8jj , GO-2026-4368

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 30%
public exploits
0
none known

Summary

Gitea's stopwatch API does not re-validate repository access permissions. After a user's access to a private repository is revoked, they may still view issue titles and repository names through previously started stopwatches.

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

Is CVE-2026-20883 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-20883 updated cvss 6.5

gitea: Gitea Stopwatch API Missing Authorization Check Leads to Post-Revocation Information Disclosure

  • Red Hat OpenShift Pipelines openshift-pipelines/pipelines-opc-rhel9, openshift-pipelines/pipelines-pipelines-as-code-cli-rhel8, openshift-pipelines/pipelines-pipelines-as-code-cli-rhel9, openshift-pipelines/pipelines-pipelines-as-code-watcher-rhel8, openshift-pipelines/pipelines-pipelines-as-code-watcher-rhel9, openshift-pipelines/pipelines-pipelines-as-code-webhook-rhel8, +3 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
9mo ago

Exploit prediction

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

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

References

Sources

Fencer Intel 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.