<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Self-Hosted-Git on CuraSec</title><link>https://curasec.metacog.co.kr/tags/self-hosted-git/</link><description>Recent content in Self-Hosted-Git on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 05 Aug 2026 13:01:27 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/self-hosted-git/index.xml" rel="self" type="application/rss+xml"/><item><title>Critical Gitea Unauthenticated File Read Fixed in 1.27.1</title><link>https://curasec.metacog.co.kr/insights/2026-08-05-critical-gitea-flaw-let-unauthenticated-attackers-read-serve/</link><pubDate>Wed, 05 Aug 2026 13:01:27 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-05-critical-gitea-flaw-let-unauthenticated-attackers-read-serve/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> Unauthenticated CVSS 9.8 file read affecting any Gitea 1.22.1–1.27.0 instance; a public repo and crafted Org-mode markup are the only prerequisites, exposing any file the service account can read (secrets, keys, configs). Patch to Gitea 1.27.1 immediately and audit service-account file permissions as a follow-up.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No public PoC, no KEV listing, and no reported active exploitation means there is no immediate detection or hunt workload; awareness is useful context for triaging future anomalous Gitea traffic if exploitation begins.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> CVE-2026-59774 — CISA KEV: not listed, EPSS n/a, no public PoC found&lt;/li>
&lt;/ul></description></item></channel></rss>