CVE-2026-26232
published 2026-07-03CVE-2026-26232: Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during token exchange.
PriorityP353critical9.1CVSS 3.1
AVNACLPRNUINSUCHIHAN
EPSS
0.38%
31.3th percentile
Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during token exchange.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| gitea | gitea_open_source_git_server | < 1.25.5 | 1.25.5 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Gitea up to 1.25.4 authentication replay
vuldb·2026-07-04
CVE-2026-26232 [LOW] Gitea up to 1.25.4 authentication replay
A vulnerability, which was classified as problematic, has been found in Gitea up to 1.25.4. Affected is an unknown function. The manipulation leads to authentication bypass by capture-replay.
This vulnerability is referenced as CVE-2026-26232. Remote exploitation of the attack is possible. No exploit is available.
It is advisable to upgrade the affected component.
GHSA
Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during token exchange.
ghsa_unreviewed·2026-07-03
CVE-2026-26232 CWE-294 Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during token exchange.
Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during token exchange.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-07-03
Published