Advisory record · GHSA-m5ch-ppfx-xv3v

Gitea OAuth2 PKCE S256 verifier bypass

CVSS 9.1 CriticalCriticalEPSS 0.0050 · 43rd percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 3 Jul 2026, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
code.gitea.io/giteaGo<1.25.51.25.5
Identifiers
GHSA-m5ch-ppfx-xv3v · CVE-2026-26247 · GO-2026-6342
Weakness (CWE)
CWE-284
Published
3 Jul 2026
Updated
2 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Gitea versions before 1.25.5 do not correctly persist the OAuth2 PKCE S256 challenge method during authorization, so the verifier check can be skipped during token exchange. The source gives few details about the exact conditions or what an attacker must already have. Upgrade to Gitea 1.25.5 or later.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.1 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0050, the 43rd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:47 UTC First seen by agentprime
  2. 31 Oct 2026, 14:47 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.