Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Gitea TOTP Guessing Vulnerability (CVE-2026-123002)

CVE-2026-123002 is an excessive authentication attempts flaw in Gitea's two-factor authentication.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-123002
Vendor
Gitea
Affected Product
Gitea
Exploitation
Not confirmed
Published
2026-11-15

CVE-2026-123002 is an excessive authentication attempts flaw in Gitea's two-factor authentication. An attacker needs a valid account password before guessing its time-based one-time passcode. Gitea fixed the missing attempt limit in version 28.4.0.Gitea says the flaw affected sign-in, password reset and Basic authentication with an OTP header. The GitHub advisory also identifies the scratch-code path as missing the control. These routes matter for organizations running their own Gitea servers and relying on TOTP to protect developer accounts.

What it allows

How Does CVE-2026-123002 Bypass Gitea TOTP?

After a correct password, Gitea previously accepted repeated wrong TOTP codes without counting failed attempts. The GitHub advisory says the same missing control affected the scratch-code path. Gitea's release note identifies password reset and Basic authentication with an OTP header as additional affected flows.

Successful guessing can give the attacker an authenticated account session despite two-factor authentication. The advisory says the attacker could then disable TOTP on that account. Optional login CAPTCHA does not cover the second-factor step, according to the advisory.

GitHub's advisory reports a successful controlled test after 309,961 attempts. That is a laboratory proof of concept, not evidence of an attack on a Gitea deployment. Brandefense Blackhole counted two matching dark chat posts from August 18 through November 16, 2026; the unit is posts, not incidents.

CISA's November 13, 2026 KEV catalog did not list this CVE. Neither the controlled test nor the two research posts establishes active exploitation. For the broader remediation workflow, see the vulnerability intelligence platform.

The multi-factor authentication glossary explains the role of a second factor. The vulnerability management guide covers tracking and verifying the fix.

Who is affected

Which Gitea Versions Are Affected by CVE-2026-123002?

The GitHub advisory lists Gitea versions through 28.3.0 as affected and 28.4.0 as patched. The advisory separately says its test used a 1.27.2 build. Because those labels use different version lines, verify the deployed build against Gitea's advisory and upgrade guidance.

Inventory self-hosted Gitea instances and record their running application version. Give priority to instances reachable by users whose passwords could be exposed, especially those using TOTP. Gitea recommends upgrading to 28.4.0 as soon as possible.

Timeline

  1. 2026-11-15

    Gitea announced 28.4.0 and described the five-failure, 15-minute account lockout.

  2. 2026-11-15

    The GitHub security advisory published the affected and patched versions and a controlled TOTP guessing test.

  3. 2026-11-15

    NVD published the CVE record, with analysis deferred at the time of the source-pack capture.

What to do

  1. Inventory and prioritize Gitea instances

    Find self-hosted Gitea deployments and record each running version. Prioritize instances through 28.3.0, especially where password-based accounts use TOTP.

  2. Upgrade to Gitea 28.4.0

    Apply Gitea's 28.4.0 security update using the supported deployment procedure. The release note says further attempts are refused for 15 minutes after five failed passcodes for an account.

  3. Verify the running version and authentication control

    After deployment, check the version reported by each running instance and confirm it is 28.4.0 or a later vendor-confirmed fixed release. Verify the updated second-factor failure control through approved administrative testing.

  4. Review account access

    Brandefense recommends reviewing unusual successful sign-ins and second-factor changes for accounts whose passwords may be compromised. Follow local incident procedures if those records indicate unauthorized access.

What Brandefense can do

Frequently Asked Questions

What is CVE-2026-123002?

It is a Gitea TOTP guessing flaw caused by missing limits on failed second-factor attempts. The attacker first needs a valid account password.

Which Gitea release fixes the flaw?

Gitea identifies 28.4.0 as the patched release. Check the version running after the upgrade, including each separately managed instance.

Does the advisory's proof of concept show real-world exploitation?

The GitHub advisory describes a successful controlled test. CISA's November 13, 2026 KEV catalog did not list the CVE; the test does not establish an incident.

Does login CAPTCHA stop the TOTP guessing path?

The GitHub advisory says optional login CAPTCHA applies to the password step, not the second-factor step. Upgrade to the patched release.

Sources

  1. MFA TOTP brute-force via missing rate limitingGitea GitHub Security Advisory
  2. Gitea 28.4.0 is releasedGitea
  3. CVE-2026-123002 DetailNational Vulnerability Database
  4. Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →