Gitea · Gitea · published 2026-11-15
CVE-2026-128359Gitea OAuth2 provider tokens issued to disabled users
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-128359 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 7% of all CVEs. This Gitea vulnerability: CVSS 5.4 (v3.1). Fixed upstream in Gitea 28.4.0, 28.3.0. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Gitea 28.4.0, 28.3.0.
Patch events
DevOpsGitea
Gitea security releases: 28.4.0, 28.3.0
Upgrade to
28.4.028.3.0Why: Vendor security release for server software (most severe: CVE-2026-118389).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (7th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.4 (v3.1)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Gitea Gitea
0to before28.4.0(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.