THREAT actors have begun exploiting a newly disclosed Docker‑related flaw in Gitea, tracked as CVE‑2026‑20896, just under two weeks after the vulnerability was made public The Hacker News reported. The bug affects the self‑hosted code‑hosting platform and allows unauthenticated attackers to bypass authentication checks and issue arbitrary requests from the compromised host. Successful exploitation can lead to full control of administrative accounts and access to internal cloud‑metadata services. The activity was observed in the wild by researchers monitoring public exploit attempts.
CVE‑2026‑20896 carries a CVSS v3 score of 9.8 and stems from a misconfiguration in the reverse proxy that forwards API requests to the Gitea backend. When the proxy does not enforce authentication before passing along certain endpoints, an attacker can call the API as if they were an authorised user. This access enables a Server‑Side Request Forgery (SSRF) chain, tracked separately as CVE‑2026‑22874, which exploits an incomplete allow‑list for outbound requests. Both issues affect Gitea versions 1.26.2 and earlier; the maintainers released version 1.26.3 to address them.
By abusing the authentication bypass, an intruder can trigger the SSRF component to send requests to internal services that are normally inaccessible from the network perimeter. This includes the cloud‑instance metadata service at 169.254.169.254, allowing the theft of temporary credentials and further lateral movement. In some cases the chain can be used to create new administrative sessions, modify repositories or push malicious code. The two vulnerabilities were disclosed together in the project’s security advisory, prompting an urgent upgrade recommendation for all self‑hosted deployments.
Exploitation attempts were first seen on 25 June 2026, only thirteen days after the advisory appeared on the Gitea security page. Scanners have been observed probing for the exposed Docker socket and trying the specific API paths that bypass the reverse‑proxy check. No specific threat‑actor group has been attributed to the activity, suggesting that opportunistic actors are leveraging public proof‑of‑concept code. The rapid timeline highlights how quickly attackers can move from disclosure to active hunting in containerised environments.
Defenders should upgrade to Gitea 1.26.3 without delay, as the patch removes the faulty proxy‑forwarding logic and tightens the SSRF allow‑list GitHub security advisory. Administrators must also verify that their reverse‑proxy configurations require valid authentication before forwarding any request to the Gitea API, regardless of the HTTP method used. Blocking outbound traffic to the instance‑metadata address and to private IP ranges at the host firewall can mitigate the impact of any remaining SSRF vectors. Detailed upgrade instructions are available in the project’s release notes.
Additional hardening steps include disabling the Docker daemon’s remote API unless absolutely required, enforcing network segmentation between build runners and the control plane, and deploying runtime‑monitoring tools that alert on outbound connections to known metadata endpoints. Maintaining an up‑to‑date software bill of materials helps verify that all dependent containers are patched. Organisations should review logs for unexpected API calls bearing administrative privileges and consider resetting any credentials that may have been exposed during the intrusion window.