Read the docs

Gitea OAuth2 provider issues tokens to disabled users

Priority LOW 23CWE-613Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-613.

Summary

Gitea before 28.4.0, when acting as an OAuth2 or OpenID Connect provider, does not check the user state at the token endpoint. Refresh tokens and unused authorization codes of users an administrator deactivated or barred from signing in can still be exchanged for new tokens (CWE-613). A remote user with low privileges can keep access after the account is disabled.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00149 4th percentileScored 2026-11-16
Fix Fixed Gitea (Gitea): 28.4.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
GiteaGiteabefore 28.4.028.4.0Patch availableCNA
  • Gitea VendorGitea Affected before 28.4.0 Fixed in 28.4.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*——Gitea
  • cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:* Versions — — ·Gitea

Remediation

Upgrade Gitea to 28.4.0 or a later release, which refuses token requests from users who may not sign in.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA Gitea (Gitea) Fixed in 28.4.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Gitea 28.4.0

    19 records Highest priority Priority LOW 19 LOW

    Other records, highest priority first

    • TI-2026-91976 Command execution in Gitea through repository auto-initializationPriority LOW 39
    • TI-2026-91985 Protected file pattern bypass in Gitea with quoted file namesPriority LOW 36
    • TI-2026-91982 Gitea missing attempt limit for TOTP passcodesPriority LOW 34

Timeline

  1. 2026-11-15 Threatist record created from CVE-2026-128359
  2. 2026-11-16 CVSS score added · CISA ADP
  3. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2026-42785 Remote code execution in Gitea diffpatch API through Git hooks KEVCVSS 3.1CRITICAL 9.8
  • TI-2026-42033 Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts CVSS 3.1CRITICAL 9.8
  • TI-2026-40842 Privilege Escalation via Access Token Scope Escalation in API CVSS 3.1CRITICAL 9.8
  • TI-2026-16922 Gitea Docker image trusts spoofable reverse-proxy headers by default CVSS 3.1CRITICAL 9.8
  • TI-2026-42043 Team-repository linking endpoint bypasses the RepoAdminChangeTeamAccess organization setting CVSS 3.1CRITICAL 9.1
  • TI-2026-40381 OIDC userinfo Endpoint Returns Identity Claims Without Enforcing API Token Scopes CVSS 3.1CRITICAL 9.1
See all 260 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences