CVE
Gitea two-factor bypass via unlimited TOTP guessing
Affects Gitea up to and including 28.3.0, but only for accounts with TOTP two-factor authentication enabled. Fixed in 28.4.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 28.4.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Account has two-factor authentication (TOTP) enabled Gitea versions up to and including 28.3.0
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.19% · 8th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Gitea, a self-hosted Git service, did not limit how many wrong TOTP passcodes could be tried during sign-in, the password reset flow, or Basic authentication using the X-Gitea-OTP header. An attacker who already knows an account's password could guess the six-digit code by trying many codes quickly and sign in despite two-factor authentication.
Original description
Gitea accepted an unlimited number of wrong TOTP passcodes during sign-in, in the password reset flow and for Basic authentication with the X-Gitea-OTP header. An attacker who already knows an account's password could guess the six-digit passcode by trying codes at a high rate and sign in despite two-factor authentication. After five failed passcodes, further attempts for the account are now refused for 15 minutes.
Who should check
Teams running Gitea 28.3.0 or earlier with two-factor authentication enabled for user accounts, including Basic auth with X-Gitea-OTP for API, git and packages
“Affected component: Gitea v1.27.2 (tested gitea/gitea:latest )”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 7.5, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Account has two-factor authentication (TOTP) enabled Gitea versions up to and including 28.3.0Upgrade to a fixed version: 28.4.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-123002 (Gitea missing attempt limit for TOTP passcodes), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-123002 (entry last updated 2026-11-16):
Affected:
- Gitea Gitea: fixed in 28.4.0
Fixed versions: 28.4.0.
Conditions (all must be true for the bug to be hit):
- Account has two-factor authentication (TOTP) enabled (source: https://github.com/go-gitea/gitea/security/advisories/GHSA-5mx6-8rwm-52wf)
- Gitea versions up to and including 28.3.0 (source: https://github.com/go-gitea/gitea/security/advisories/GHSA-5mx6-8rwm-52wf)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-123002 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123002 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/go-gitea/gitea/security/advisories/GHSA-5mx6-8rwm-52wf
- https://github.com/go-gitea/gitea/pull/39993
- https://github.com/go-gitea/gitea/pull/40374
- https://blog.gitea.com/release-of-28.4.0/
- https://github.com/go-gitea/gitea/releases/tag/v28.4.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-123002
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123002"}.Timeline
- CVE published
- First seen by cve.now1 day
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- gitea.dev
fixed in 28.4.0
Evidence 7
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Advisory
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Patch
- Patch
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123002
Is CVE-2026-123002 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Gitea does not limit how many TOTP passcode guesses are allowed at sign-in. An attacker who already knows the account password could guess the six-digit code, gain a fully authenticated session as the victim, and disable the victim's TOTP.Source: github.com
Which versions are affected by CVE-2026-123002?
gitea.dev: before 28.4.0.Source: cve.now feed data
Am I affected, and how do I check?
Gitea versions up to and including 28.3.0 are in the affected range, and the bug only matters for accounts with TOTP two-factor authentication enabled. To check, look at the Gitea version in use and at whether TOTP is enabled in the account's security settings.Source: github.com
How do I fix CVE-2026-123002?
Upgrade Gitea to 28.4.0, the listed fixed version.Source: github.com