Skip to content

Gitea OAuth2 authorization codes can be reused after expiry

Critical severity GitHub Reviewed Published Jul 3, 2026 to the GitHub Advisory Database • Updated Sep 1, 2026

Package

gomod code.gitea.io/gitea (Go)

Affected versions

< 1.25.5

Patched versions

1.25.5

Description

Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during token exchange.

References

Published by the National Vulnerability Database Jul 3, 2026
Published to the GitHub Advisory Database Jul 3, 2026
Last updated Sep 1, 2026
Reviewed Sep 1, 2026

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(40th percentile)

Weaknesses

Authentication Bypass by Capture-replay

A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes). Learn more on MITRE.

CVE ID

CVE-2026-26232

GHSA ID

GHSA-5v69-g2m3-3hq3

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.