dbcve.org
CWE-294Weakness · CWE-294

CVE-2026-26232

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-03
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Gitea versions before 1.25.5 fail to properly enforce OAuth2 authorization code expiration and single-use constraints during token exchange, potentially allowing attackers to reuse authorization codes to obtain unauthorized access tokens.

MitigationUpgrade Gitea to version 1.25.5 or later to apply the patch that properly enforces OAuth2 authorization code expiry and single-use behavior.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Gitea version
    Run `gitea --version` or check the admin dashboard UI footer to find the installed version number
    Affected if The installed version is earlier than 1.25.5 (for example, 1.25.4, 1.24.x, or earlier)
  2. Confirm OAuth2 authentication is in use
    Inspect the Gitea authentication configuration (via admin panel or configuration file) to verify that at least one OAuth2 provider is enabled
    Affected if OAuth2 providers are configured and active in the Gitea instance
  3. Check OAuth2 provider settings
    Review the OAuth2 provider configuration in `app.ini` or through the web admin interface to confirm authorization code flow is in use
    Affected if OAuth2 providers are configured to use the authorization code grant type

You are affected if your Gitea version is before 1.25.5 AND you have OAuth2 authentication providers configured using the authorization code flow.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Gitea to version 1.25.5 or later to apply the patch that properly enforces OAuth2 authorization code expiry and single-use behavior.

Recommended fix High confidence

1.25.5

  1. Back up your current Gitea instance (database, configuration, and repository data)
  2. Stop the running Gitea service
  3. Download Gitea version 1.25.5 from the official releases (e.g., https://github.com/go-gitea/gitea/releases/tag/v1.25.5)
  4. Replace the existing Gitea binary with the new version
  5. Verify file permissions are correct for the new binary
  6. Start the Gitea service
  7. Verify the upgrade was successful by checking the Gitea version in the admin panel or via command line
  8. Test OAuth2 authentication flows to confirm the vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26232 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26232 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data