Skip to main content
Menu
CVEs

CVE

Gitea disabled accounts retain access via OAuth2 tokens

CVE-2026-128359EUVD-2026-126129

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

5.4MediumCISA-ADP
Exploited
No known exploitation
Fix
Fixed in 28.4.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 28.4.0.

Published
Last modified
Reference
Last checked
0.15% · 4th percentile
8/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Gitea, when acting as an OAuth2 or OpenID Connect provider, did not check whether a user was still allowed to sign in, so refresh tokens and unused authorization codes from deactivated or sign-in-prohibited accounts could still be exchanged for new tokens. As a result, applications that sign users in through Gitea could keep those users signed in after an administrator had disabled them.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

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.

cve.now Index

8Pcve.now Index 8 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.4/10CVSS 5.4
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 28.4.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-128359 (Gitea OAuth2 provider tokens issued to disabled users), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128359 (entry last updated 2026-11-16):
Affected:
- Gitea Gitea: fixed in 28.4.0
Fixed versions: 28.4.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-128359 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128359 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/go-gitea/gitea/security/advisories/GHSA-jrjr-q3rq-f899
- https://github.com/go-gitea/gitea/pull/40131
- https://github.com/go-gitea/gitea/pull/40281
- https://blog.gitea.com/release-of-28.4.0/
- https://github.com/go-gitea/gitea/releases/tag/v28.4.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128359
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128359"}.

Timeline

  1. CVE published
  2. First seen by cve.now1 day
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • gitea.dev

    fixed in 28.4.0

Evidence 7

Vendor advisory · 2

Establishes: Affected and fixed versions.

  1. Advisory
  2. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Patch
  2. Patch
  3. Repository

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-128359

Is CVE-2026-128359 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-128359?

gitea.dev: before 28.4.0.Source: cve.now feed data

How do I fix CVE-2026-128359?

Upgrade to a fixed version: 28.4.0.Source: cve.now feed data