Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-96404 – Authentication Bypass (Admin Account Takeover) – Gitea ≤1.27.3

Be the first to know when new zero-days emerge:

Summary

CVE-2026-96404 is an authentication bypass in Gitea’s web installer that allows an attacker to obtain an authenticated session for an existing user account — including an administrator account — without supplying a valid password. The flaw affects Gitea v1.27.3 and earlier when the /install installer endpoint is reachable against a database that already contains user records, and it carries a CVSS v3.1 base score of 8.1 (High).

Technical details

  • Root cause: when the installer’s CreateUser call fails with ErrUserAlreadyExist (because the submitted username already exists in the database), Gitea falls back to loading the existing user record via GetUserByName and proceeds to issue an authenticated session token without ever verifying the submitted password.
  • A related safeguard, HasPostInstallationUsers(), which is meant to block the installer from running again once the instance is already populated, only triggers when 2 or more users exist — so databases containing a single (admin) account skip the reinstall confirmation entirely.
  • Trigger conditions: the installer is reachable when INSTALL_LOCK is false against a database that already has data. This can occur in real deployments where application storage (e.g., a container volume or PVC) is re-provisioned or restored separately from the backing database, causing Gitea to think it is a fresh install while the database still holds existing accounts.
  • Attack vector: network, unauthenticated, requires no user interaction. An attacker submits the install form using a username that matches an existing (ideally administrator) account; no correct password is required.
  • Impact: the attacker is granted a fully authenticated session for that account. If the matched account is an administrator, this yields complete administrative control of the Gitea instance, including the ability to change the account’s password and lock out the legitimate owner.

Affected software

  • Gitea versions up to and including v1.27.3
  • Fixed in Gitea v28.0.0

Severity

  • CVSS v3.1 Base Score: 8.1 (High)
  • Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Weakness classification: CWE-287 (Improper Authentication) / CWE-306 (Missing Authentication for Critical Function)

Mitigation and recommended actions

  • Immediate: upgrade to Gitea v28.0.0 or later, which removes the silent fallback to an existing account and issuance of a session without password verification, and corrects the reinstall-confirmation check.
  • If an immediate upgrade is not possible:
    • Ensure INSTALL_LOCK is set to true in app.ini on every running instance and verify it is not reset when storage/volumes are redeployed or restored.
    • Make sure the /install path is never reachable from the network once an instance has been initialized — restrict it at the network/proxy layer as defense in depth.
    • Audit deployment pipelines (containers, PVCs, backups) to ensure application data volumes and the backing database are always provisioned/restored together, preventing a state where the app believes it is uninstalled while the database retains existing users.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge