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.

Share this

Remediation#

Fixed upstream in Gitea 28.4.0, 28.3.0.

Patch events

  1. This monthSecurity release

    DevOpsGitea

    Gitea security releases: 28.4.0, 28.3.0

    Upgrade to 28.4.028.3.0

    Why: Vendor security release for server software (most severe: CVE-2026-118389).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (7th pct)FIRST EPSS v2026.06.15
CVSS base score5.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 exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

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.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →