Habr•July 21, 2026•🇷🇺Translated from Russian

Gitea Authentication Bypass Exposes Private Repositories Through Default Docker Reverse Proxy Setting

A critical authentication bypass vulnerability has been demonstrated in Gitea, allowing attackers to impersonate administrators and access private repositories simply by sending one HTTP header. The flaw, assigned CVE-2026-20896 and rated 9.8 on the CVSS scale, stems from a dangerous default in the official Docker image that trusts the X-WEBAUTH-USER header from any IP address.

Root Cause and Attack Flow

Gitea supports authentication via a reverse proxy for single sign-on scenarios. When enabled, the proxy authenticates the user and passes the username in the X-WEBAUTH-USER header. The application trusts this header only from addresses listed in the REVERSE_PROXY_TRUSTED_PROXIES configuration option. In the official Docker image the default value was set to a wildcard (“*”), meaning any source could supply the header.

An attacker could therefore send a request such as:

  • curl -H 'X-WEBAUTH-USER: admin' http://target:3000/admin/secret-infra/raw/branch/main/.env

and immediately retrieve the contents of a private repository file containing production secrets.

Additional Related Vulnerabilities

The same pattern of broken access control appeared in several other Gitea components throughout 2026:

  • CVE-2026-27771 – private container images were served anonymously through the built-in OCI registry.
  • CVE-2026-22874 – an overly permissive allow-list allowed SSRF via webhooks and migrations.
  • CVE-2026-28740 – authorization bypass in LFS permitted reading objects from private repositories without proper rights.

These issues affected both Gitea and its fork Forgejo, impacting tens of thousands of internet-facing instances.

Recommended Mitigations

Administrators are advised to:

  • Upgrade to Gitea 1.26.4 or newer (avoid 1.26.3 due to a regression in the SSRF fix).
  • Explicitly configure REVERSE_PROXY_TRUSTED_PROXIES to the IP or CIDR of the actual reverse proxy.
  • Disable reverse-proxy authentication if it is not required.
  • Place Gitea behind a reverse proxy or WAF and monitor logs for 200 responses to administrative paths from unexpected source IPs.

The researcher emphasizes that the incident is not an isolated coding error but a systemic problem caused by overly permissive defaults in official container images.

Related articles

Habr•Vulnerabilities & Exploits

PHP Prepares Critical Patches for All Supported Versions One Month After Emergency Update

The PHP development team announced on November 18 that it will release updates for all supported interpreter versions to address multiple vulnerabilities, including critical ones. The fixes target a use-after-free flaw in file upload progress tracking that can lead to remote code execution when specific session serialization formats are combined. This comes shortly after emergency patches issued on October 21 resolved two remote code execution issues collectively known as PHP2Shell. The new vulnerability, tracked as CVE-2026-115560 with a CVSS score of 9.8, arises when applications switch session formats from php_binary or php_serialize to php after upload tracking has begun. Developers are advised to disable session.upload_progress.enabled until patches are applied and verified. Releases are scheduled for November 19 between 17:00 and 17:30 Moscow time, accompanied by a detailed security bulletin.

Security NEXT•Vulnerabilities & Exploits

WordPress 7.1.5 Released to Patch Multiple Vulnerabilities Including Privilege Escalation

The WordPress development team has issued version 7.1.5 to resolve more than 20 security issues spanning privilege escalation, remote code execution risks, SQL injection, and cross-site scripting flaws. The update specifically addresses an attribute-based vulnerability in the Template Part block that could allow attackers to escalate privileges and potentially execute arbitrary code. A separate flaw in multisite environments enables site administrators to hijack super-admin accounts by abusing the customizer menu preview feature. Two SQL injection vulnerabilities and multiple XSS issues were also corrected, along with information disclosure problems. Sites configured for automatic background updates will receive the patch automatically, while manual updates remain available through the admin dashboard. Backports are being rolled out for branches starting from WordPress 4.7.

Security NEXT•Vulnerabilities & Exploits

CISA Adds Four Actively Exploited Vulnerabilities to KEV Catalog Targeting Apache Axis, REDCap, Synology DSM and LiteLLM

The U.S. Cybersecurity and Infrastructure Security Agency has added four vulnerabilities to its Known Exploited Vulnerabilities catalog after confirming active exploitation in the wild. The flaws affect Apache Axis, REDCap, Synology DSM, and LiteLLM, prompting mandatory remediation for federal agencies. CVE-2026-90436 in Apache Axis allows unauthenticated remote code execution via crafted SOAP fault messages under specific conditions. CVE-2026-90817 in REDCap enables unauthenticated remote code execution through manipulated HTTP requests targeting public survey and data import functions, provided an attacker knows a valid survey hash. The remaining two vulnerabilities in Synology DSM and LiteLLM were also confirmed exploited but lack detailed public descriptions at this time. Organizations are urged to apply patches immediately to prevent further attacks.

AntiMalware•Vulnerabilities & Exploits

NGINX Patches Critical Remote Code Execution Vulnerability Present Since 2015 (CVE-2026-123007)

NGINX has released patches for a critical vulnerability, CVE-2026-123007, that allowed unauthenticated remote code execution on servers with HTTP/2 enabled. The flaw existed in the codebase since version 1.9.5 released in 2015 and was fixed in versions 1.30.7 and 1.31.9 on November 18. Researchers at Wiz discovered that improper handling of HTTP/2 flow control counters leads to memory corruption, enabling code execution that bypasses ASLR and runs with the privileges of the NGINX worker process. The vulnerability affects even servers serving only static files without backend application connections. A second related issue, CVE-2026-123633, involving use-after-free in HTTP/2 handling, was also addressed in the same updates. Administrators are advised to apply the patches immediately or disable HTTP/2 as a temporary mitigation if updates cannot be installed promptly. No in-the-wild exploitation of CVE-2026-123007 had been observed at the time of disclosure.