<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gitea on CuraSec</title><link>https://curasec.metacog.co.kr/tags/gitea/</link><description>Recent content in Gitea on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 11 Jul 2026 11:49:48 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/gitea/index.xml" rel="self" type="application/rss+xml"/><item><title>Critical auth bypass in Gitea Docker image under active exploitation</title><link>https://curasec.metacog.co.kr/insights/2026-07-11-hackers-exploit-critical-auth-bypass-in-gitea-docker-image/</link><pubDate>Sat, 11 Jul 2026 11:49:48 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-11-hackers-exploit-critical-auth-bypass-in-gitea-docker-image/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> If you run Gitea via the official Docker image, update to the patched image immediately — the flaw allows full admin impersonation and is being actively exploited. Audit recent repository access and check for unauthorized commits or access token creation.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Act:&lt;/strong> Active exploitation of an admin-impersonation bug in a self-hosted code repository warrants an assume-breach sweep: review Gitea audit logs for anomalous authentication events or unexpected admin-level actions since the vulnerability became public, and hunt for signs of unauthorized repository access or code changes.&lt;/li>
&lt;li>&lt;strong>Leader — Act:&lt;/strong> If your organization self-hosts Gitea via Docker, confirm with engineering this week whether the vulnerable image is in use and verify patching status — unauthorized admin access to source code repositories is a direct supply chain and IP risk.&lt;/li>
&lt;/ul></description></item></channel></rss>