Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-20896 – Authentication Bypass – Gitea Docker Image ≤ 1.26.2

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

Summary

CVE-2026-20896 is a critical authentication bypass vulnerability (CVSS 9.8) in the official Gitea Docker image, affecting all versions up to and including 1.26.2. The flaw stems from a dangerous default configuration in the Docker image that allows any IP address on the internet to inject an arbitrary user identity via an HTTP header, resulting in complete unauthenticated access to the Gitea instance. Patches are available in Gitea 1.26.3 and 1.26.4.

Technical details

  • Root cause: The Gitea Docker image ships with REVERSE_PROXY_TRUSTED_PROXIES = * in its default configuration, causing Gitea to trust reverse-proxy authentication headers from any source IP address — rather than restricting trust to loopback or internal addresses as documented.
  • Trigger conditions: The vulnerability is exploitable when reverse-proxy authentication is enabled (ENABLE_REVERSE_PROXY_AUTHENTICATION = true). The Docker image’s wildcard trusted-proxy setting is what enables unauthenticated exploitation from any network location.
  • Attack vector: A remote, unauthenticated attacker sends a single crafted HTTP request to the Gitea instance with the header X-WEBAUTH-USER: <target_username> (e.g., X-WEBAUTH-USER: admin). Because the wildcard configuration accepts any source IP as a trusted proxy, Gitea authenticates the request using the supplied header value without any credential verification.
  • Impact: Successful exploitation grants the attacker full access as the impersonated user. Targeting an administrator account results in complete platform compromise, including: read access to all private repositories, injection of SSH keys, extraction of CI/CD secrets, modification of webhooks (enabling potential lateral movement via SSRF), and — where auto-registration is enabled — creation of arbitrary accounts.

Affected software

  • Gitea Docker image, all versions ≤ 1.26.2, when ENABLE_REVERSE_PROXY_AUTHENTICATION is set to true

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate — upgrade: Update the Gitea Docker image to version 1.26.4 (recommended) or 1.26.3. The patched releases correct the Docker image’s default configuration so that only loopback connections are trusted as reverse-proxy sources.
  • If immediate patching is not possible: Explicitly set REVERSE_PROXY_TRUSTED_PROXIES to the specific IP address(es) of your upstream reverse proxy (e.g., 127.0.0.1 or 172.18.0.1) rather than the wildcard *. Additionally, ensure ENABLE_REVERSE_PROXY_AUTHENTICATION is disabled unless actively required.
  • Network mitigation: Restrict direct internet access to the Gitea HTTP port so that the X-WEBAUTH-USER header cannot be injected from untrusted sources.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

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