How severe is CVE-2026-26232?

CVE-2026-26232 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-26232 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (41st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-26232?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-26232 published?

CVE-2026-26232 was published on 2026-07-03 and last updated on 2026-07-07.

CVE-2026-26232

CVE-2026-26232 is a critical-severity vulnerability with a CVSS 3.x base score of 9.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-294.

Key facts

Severity: Critical (CVSS 3.x base score 9.1)
EPSS exploit prediction: 0% (41st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-294
Published: 2026-07-03
Last modified: 2026-07-07

Description

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

Frequently asked questions

What is CVE-2026-26232?: Gitea versions before 1.25.5 do not consistently enforce OAuth2 authorization code expiry and single-use behavior during token exchange.
How severe is CVE-2026-26232?: CVE-2026-26232 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-26232 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (41st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-26232?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-26232 published?: CVE-2026-26232 was published on 2026-07-03 and last updated on 2026-07-07.

References

Other CWE-294 (Authentication Bypass by Capture-replay) vulnerabilities

CVE-2025-49752 — Critical (CVSS 10.0): Azure Bastion Elevation of Privilege Vulnerability
CVE-2026-88278 — Critical (CVSS 9.8): GeoVision GV-LPC2211 V1.13 fails to enforce WS-Security UsernameToken freshness or nonce reuse protection, allowing a…
CVE-2026-86219 — Critical (CVSS 9.8): Authen::SASL::Perl::DIGEST_MD5 versions before 2.2100 for Perl accept replayed authentication responses via unverified…
CVE-2026-65905 — Critical (CVSS 9.8): Authentication Bypass by Capture-replay vulnerability in Apache Tomcat's DIGEST authenticator. If, before windowSize…
CVE-2026-68079 — Critical (CVSS 9.8): In Apache CXF's DefaultEncryptingCodeDataProvider, a captured authorization code can be redeemed an unlimited number…
CVE-2026-28564 — Critical (CVSS 9.8): Insufficient Session Expiration, Authentication Bypass by Capture-replay vulnerability in Apache IoTDB. REST Basic…

Browse all CWE-294 (Authentication Bypass by Capture-replay) vulnerabilities →