Skip to content
Fencer Intel
medium 5.4

CVE-2026-128359 json

Gitea OAuth2 provider tokens issued to disabled users

published 2d ago modified yesterday also EUVD-2026-126129 , GHSA-jrjr-q3rq-f899

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository go-gitea/gitea. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

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

Summary

When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. After an administrator deactivated an account or prohibited its sign-in, existing refresh tokens and unused authorization codes of that user could still be exchanged for new tokens, so applications that sign users in through Gitea kept them signed in. The token endpoint now refuses users who may not sign in, and token introspection reports their tokens as inactive.

Patch / fix

  • go gitea.dev 28.4.0
  • Gitea Gitea 28.4.0

Is CVE-2026-128359 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
yesterday

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go gitea.dev
<=28.3.0
28.4.0

Affected products

  • Gitea Gitea

Classification

Weakness
  • CWE-613 DEPRECATED: Insufficient Session Expiration
Technology feeds

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.

The maintainers of go-gitea/gitea published their own advisory on GitHub. Reviewed sources take precedence over it.