Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.4%top 69%

CVE-2026-26247: CWE-284 in Gitea Gitea Open Source Git Server

0
Critical
VulnerabilityCVE-2026-26247cvecve-2026-26247cwe-284
Published: 07/03/2026 (07/03/2026, 20:19:34 UTC)
Source: CVE Database V5
Vendor/Project: Gitea
Product: Gitea Open Source Git Server

Description

Gitea versions before 1.25.5 do not persist the OAuth2 PKCE S256 challenge method correctly during authorization, allowing token exchange without the expected verifier check.

CVSS v3.1

Score 9.1critical

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected software

github.com/go-gitea/gitea
pkg:golang/github.com/go-gitea/gitea
Affected versions
<1.25.5

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/11/2026, 08:45:52 UTC

Technical Analysis

CVE-2026-26247 affects Gitea Open Source Git Server versions before 1.25.5. The issue arises because the OAuth2 PKCE S256 challenge method is not properly persisted during the authorization process, which allows token exchange without verifying the expected code verifier. This improper access control weakness (CWE-284) can lead to unauthorized token issuance, compromising confidentiality and integrity of user sessions. The vulnerability has a CVSS v3.1 base score of 9.1, indicating critical severity with network attack vector, low attack complexity, no privileges required, no user interaction, and high impact on confidentiality and integrity.

Potential Impact

Successful exploitation of this vulnerability allows an attacker to bypass the OAuth2 PKCE verifier check and obtain access tokens without proper authorization. This can lead to unauthorized access to user accounts and sensitive repository data, compromising confidentiality and integrity. Availability is not impacted.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch link is provided, users should monitor Gitea's official channels for updates and apply the patch once available. Until then, consider restricting OAuth2 token exchanges or applying compensating controls to limit exposure.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Gitea
Date Reserved
2026-03-03T03:25:28.654Z
Cvss Version
null
State
PUBLISHED
Remediation Level
null

Threat ID: 6a4820fc27e9c79719acbf9d

Added to database: 07/03/2026, 20:52:12 UTC

Last enriched: 07/11/2026, 08:45:52 UTC

Last updated: 08/11/2026, 00:41:11 UTC

Views: 77

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses