# CVE-2026-123002: Gitea missing attempt limit for TOTP passcodes

> Attackers knowing a Gitea password can brute-force the TOTP passcode to bypass two-factor authentication.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 15 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-5mx6-8rwm-52wf

## What is CVE-2026-123002?

CVE-2026-123002 is a high-severity authentication bypass vulnerability in Gitea, published on 15 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-123002?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-123002?

No fix has been published for CVE-2026-123002 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123002 being exploited?

There is no known exploitation of CVE-2026-123002 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123002 and fix it if it is affected.

What it is: CVE-2026-123002 is a high-severity authentication bypass vulnerability in Gitea, published on 15 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-123002 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: Gitea. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123002/ (Markdown: https://insights.sbomify.com/CVE-2026-123002/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123002
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123002
- OSV: https://osv.dev/vulnerability/CVE-2026-123002

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123002/
Summaries are generated and may contain mistakes; the official description above is the record.
