Hackers are actively exploiting a critical vulnerability in the official Docker image for the Gitea self-hosted Git service that allows attackers to impersonate any user, including administrators. The security flaw is an authentication bypass vulnerability, tracked as CVE-2026-20896, that affects deployments using the default configuration, where reverse proxy authentication headers such as X-WEBAUTH-USER are enabled. Michael Clark, leading security researcher at Sysdig, confirmed that exploitation of the flaw started less than two weeks before the vulnerability was publicly disclosed. Currently, there are around 6,200 Gitea instances exposed on the public web, although it is unclear how many of them are vulnerable. “Gitea's official Docker image ships `REVERSE_PROXY_TRUSTED_PROXIES=*`. With reverse-proxy authentication enabled, Gitea then trusts the `X-WEBAUTH-USER` header from any source IP so an unauthenticated internet client becomes whoever it claims to be,” Clark warned. “No password. No token. One header. Sysdig sensors caught the first in-the-wild hit 13 days after the advisory, a VPN-exit scanner that grabbed access.” Gitea is an open-source self-hosted alternative to GitHub and GitLab, used to store source code, manage pull requests, collaborate, deploy, and perform CI/CD operations. Gitea's official Docker image configured reverse-proxy authentication to trust identity headers from any client IP address rather than only from trusted reverse proxies, allowing unaut...
Hackers exploit critical auth bypass in Gitea Docker image
BleepingComputer
·Bill Toulas
·Published Jul 10, 2026
·Updated
Affected Software
2 affected components
Gitea official Docker image for Gitea self-hosted Git service<=1.26.2
Gitea Gitea self-hosted Git service (default configuration with reverse proxy auth headers enabled)<=1.26.2
Frequently Asked Questions
1
What is the main topic of this article?
The article discusses a critical authentication bypass vulnerability in the official Gitea Docker image that is being actively exploited by hackers.
2
What security implications are discussed in the article?
The vulnerability allows attackers to impersonate any user, including administrators, which can lead to unauthorized access and control over the Gitea service.
3
What is the tracking identifier for the vulnerability mentioned?
The vulnerability is tracked as CVE-2026-20896.
4
What products or software are affected by this vulnerability?
The affected products include the Gitea official Docker image and the Gitea self-hosted Git service with default configurations that have reverse proxy authentication headers enabled.
5
When was this vulnerability first published?
The vulnerability was published on July 10, 2026.