<?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>Tue, 06 Oct 2026 22:32:59 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-334034</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-334034</link>
      <description>EUVD-2026-334034</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-334034</guid>
    </item>
    <item>
      <title>fkie_cve-2026-55430</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-55430</link>
      <description>&lt;p&gt;Coder allows organizations to provision remote development environments via Terraform. Prior to versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2, the workspace app proxy resolves the target app from `httpapi.RequestHost()` which prefers the `X-Forwarded-Host` header over the real `Host` header. No middleware strips `X-Forwarded-Host` before routing and the header is not browser-forbidden so client-side JavaScript can set it on `fetch()` calls. Practical exploitation requires subdomain app routing (wildcard hostname) enabled, a victim who visits the attacker&amp;#39;s shared app and a deployment whose upstream proxy does not strip `X-Forwarded-Host`. The fix in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2 trusts `X-Forwarded-Host` only from configured trusted proxies and otherwise resolves the routing host from the verified request host. As a workaround, place an upstream reverse proxy that strips or overwrites `X-Forwarded-Host` on untrusted requests.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Coder allows organizations to provision remote development environments via Terraform. Prior to versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2, the workspace app proxy resolves the target app from `httpapi.RequestHost()` which prefers the `X-Forwarded-Host` header over the real `Host` header. No middleware strips `X-Forwarded-Host` before routing and the header is not browser-forbidden so client-side JavaScript can set it on `fetch()` calls. Practical exploitation requires subdomain app routing (wildcard hostname) enabled, a victim who visits the attacker&amp;#39;s shared app and a deployment whose upstream proxy does not strip `X-Forwarded-Host`. The fix in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2 trusts `X-Forwarded-Host` only from configured trusted proxies and otherwise resolves the routing host from the verified request host. As a workaround, place an upstream reverse proxy that strips or overwrites `X-Forwarded-Host` on untrusted requests.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-55430</guid>
    </item>
    <item>
      <title>GHSA-5g4w-3vw9-478w — Coder's subdomain workspace app routing trusts unauthenticated X-Forwarded-Host header, enabling cross-app data access</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5g4w-3vw9-478w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/coder/coder/v2&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The workspace app proxy resolves the target app from `httpapi.RequestHost()` which prefers the `X-Forwarded-Host` header over the real `Host` header. No middleware strips `X-Forwarded-Host` before routing and the header is not browser-forbidden so client-side JavaScript can set it on `fetch()` calls.&lt;/p&gt;
&lt;p&gt;&amp;gt; **Note:** Practical exploitation requires subdomain app routing (wildcard hostname) enabled, a victim who visits the attacker&amp;#39;s shared app and a deployment whose upstream proxy does not strip `X-Forwarded-Host`.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;App session cookies are scoped to the wildcard parent domain so the browser attaches them to any app subdomain. An attacker who controls a shared workspace app can serve JavaScript that sends same-site requests with a forged `X-Forwarded-Host` pointing at a victim&amp;#39;s private app. The server routes by the attacker-controlled header but authorizes with the victim&amp;#39;s cookie which lets the attacker read the victim&amp;#39;s private app responses. Subdomain app routing must be enabled and no upstream proxy may strip `X-Forwarded-Host`.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The fix trusts `X-Forwarded-Host` only from configured trusted proxies and otherwise resolves the routing host from the verified request host.&lt;/p&gt;
&lt;p&gt;The fix was backported to all supported release lines:&lt;/p&gt;
&lt;p&gt;| Release line | Patched version |
|---|---|
| 2.34 | [v2.34.2](https://github.com/coder/coder/releases/tag/v2.34.2) |
| 2.33 | [v2.33.8](https://github.com/coder/coder/releases/tag/v2.33.8) |
| 2.32 | [v2.32.7](htt…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/coder/coder/v2&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The workspace app proxy resolves the target app from `httpapi.RequestHost()` which prefers the `X-Forwarded-Host` header over the real `Host` header. No middleware strips `X-Forwarded-Host` before routing and the header is not browser-forbidden so client-side JavaScript can set it on `fetch()` calls.&lt;/p&gt;
&lt;p&gt;&amp;gt; **Note:** Practical exploitation requires subdomain app routing (wildcard hostname) enabled, a victim who visits the attacker&amp;#39;s shared app and a deployment whose upstream proxy does not strip `X-Forwarded-Host`.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;App session cookies are scoped to the wildcard parent domain so the browser attaches them to any app subdomain. An attacker who controls a shared workspace app can serve JavaScript that sends same-site requests with a forged `X-Forwarded-Host` pointing at a victim&amp;#39;s private app. The server routes by the attacker-controlled header but authorizes with the victim&amp;#39;s cookie which lets the attacker read the victim&amp;#39;s private app responses. Subdomain app routing must be enabled and no upstream proxy may strip `X-Forwarded-Host`.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The fix trusts `X-Forwarded-Host` only from configured trusted proxies and otherwise resolves the routing host from the verified request host.&lt;/p&gt;
&lt;p&gt;The fix was backported to all supported release lines:&lt;/p&gt;
&lt;p&gt;| Release line | Patched version |
|---|---|
| 2.34 | [v2.34.2](https://github.com/coder/coder/releases/tag/v2.34.2) |
| 2.33 | [v2.33.8](https://github.com/coder/coder/releases/tag/v2.33.8) |
| 2.32 | [v2.32.7](htt…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5g4w-3vw9-478w</guid>
    </item>
  </channel>
</rss>
