<?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>Fri, 02 Oct 2026 15:29:31 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-273768</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-273768</link>
      <description>EUVD-2026-273768</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-273768</guid>
    </item>
    <item>
      <title>fkie_cve-2026-27588</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-27588</link>
      <description>&lt;p&gt;Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, Caddy&amp;#39;s HTTP `host` request matcher is documented as case-insensitive, but when configured with a large host list (&amp;gt;100 entries) it becomes case-sensitive due to an optimized matching path. An attacker can bypass host-based routing and any access controls attached to that route by changing the casing of the `Host` header. Version 2.11.1 contains a fix for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, Caddy&amp;#39;s HTTP `host` request matcher is documented as case-insensitive, but when configured with a large host list (&amp;gt;100 entries) it becomes case-sensitive due to an optimized matching path. An attacker can bypass host-based routing and any access controls attached to that route by changing the casing of the `Host` header. Version 2.11.1 contains a fix for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-27588</guid>
    </item>
    <item>
      <title>GHSA-x76f-jf84-rqj8 — Caddy: MatchHost becomes case-sensitive for large host lists (&gt;100), enabling host-based route/auth bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x76f-jf84-rqj8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/caddyserver/caddy/v2&lt;/p&gt;
&lt;p&gt;### Summary
Caddy&amp;#39;s HTTP `host` request matcher is documented as case-insensitive, but when configured with a large host list (&amp;gt;100 entries) it becomes case-sensitive due to an optimized matching path. An attacker can bypass host-based routing and any access controls attached to that route by changing the casing of the `Host` header.&lt;/p&gt;
&lt;p&gt;### Details
In Caddy `v2.10.2`, the `MatchHost` matcher states it matches the Host value case-insensitively:&lt;/p&gt;
&lt;p&gt;- `modules/caddyhttp/matchers.go`: `type MatchHost matches requests by the Host value (case-insensitive).`&lt;/p&gt;
&lt;p&gt;However, in `MatchHost.MatchWithError`, when the host list is considered &amp;#34;large&amp;#34; (`len(m) &amp;gt; 100`):&lt;/p&gt;
&lt;p&gt;- `MatchHost.large()` returns true for `len(m) &amp;gt; 100` (`modules/caddyhttp/matchers.go`, around the `large()` helper).
- The matcher takes a &amp;#34;fast path&amp;#34; using binary search over the sorted host list, and checks for an exact match using a case-sensitive string comparison (`m[pos] == reqHost`).
- After the fast path fails, the fallback loop short-circuits for large lists by breaking as soon as it reaches the first non-fuzzy entry. For configs comprised of exact hostnames only (no wildcards/placeholders), this prevents the `strings.EqualFold(reqHost, host)` check from ever running.&lt;/p&gt;
&lt;p&gt;Net effect: with a host list length of 101 or more, changing only the casing of the incoming `Host` header can cause the `host` matcher to not match when it should.&lt;/p&gt;
&lt;p&gt;#### Suggested fix
- Normalize exact hostnames to lower-case during `MatchHost.Provision` (a…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/caddyserver/caddy/v2&lt;/p&gt;
&lt;p&gt;### Summary
Caddy&amp;#39;s HTTP `host` request matcher is documented as case-insensitive, but when configured with a large host list (&amp;gt;100 entries) it becomes case-sensitive due to an optimized matching path. An attacker can bypass host-based routing and any access controls attached to that route by changing the casing of the `Host` header.&lt;/p&gt;
&lt;p&gt;### Details
In Caddy `v2.10.2`, the `MatchHost` matcher states it matches the Host value case-insensitively:&lt;/p&gt;
&lt;p&gt;- `modules/caddyhttp/matchers.go`: `type MatchHost matches requests by the Host value (case-insensitive).`&lt;/p&gt;
&lt;p&gt;However, in `MatchHost.MatchWithError`, when the host list is considered &amp;#34;large&amp;#34; (`len(m) &amp;gt; 100`):&lt;/p&gt;
&lt;p&gt;- `MatchHost.large()` returns true for `len(m) &amp;gt; 100` (`modules/caddyhttp/matchers.go`, around the `large()` helper).
- The matcher takes a &amp;#34;fast path&amp;#34; using binary search over the sorted host list, and checks for an exact match using a case-sensitive string comparison (`m[pos] == reqHost`).
- After the fast path fails, the fallback loop short-circuits for large lists by breaking as soon as it reaches the first non-fuzzy entry. For configs comprised of exact hostnames only (no wildcards/placeholders), this prevents the `strings.EqualFold(reqHost, host)` check from ever running.&lt;/p&gt;
&lt;p&gt;Net effect: with a host list length of 101 or more, changing only the casing of the incoming `Host` header can cause the `host` matcher to not match when it should.&lt;/p&gt;
&lt;p&gt;#### Suggested fix
- Normalize exact hostnames to lower-case during `MatchHost.Provision` (a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x76f-jf84-rqj8</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-27588</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-27588</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:24.04:LTS: caddy, Ubuntu:25.10: caddy, Ubuntu:Pro:26.04:LTS: caddy&lt;/p&gt;
&lt;p&gt;Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, Caddy&amp;#39;s HTTP `host` request matcher is documented as case-insensitive, but when configured with a large host list (&amp;gt;100 entries) it becomes case-sensitive due to an optimized matching path. An attacker can bypass host-based routing and any access controls attached to that route by changing the casing of the `Host` header. Version 2.11.1 contains a fix for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:24.04:LTS: caddy, Ubuntu:25.10: caddy, Ubuntu:Pro:26.04:LTS: caddy&lt;/p&gt;
&lt;p&gt;Caddy is an extensible server platform that uses TLS by default. Prior to version 2.11.1, Caddy&amp;#39;s HTTP `host` request matcher is documented as case-insensitive, but when configured with a large host list (&amp;gt;100 entries) it becomes case-sensitive due to an optimized matching path. An attacker can bypass host-based routing and any access controls attached to that route by changing the casing of the `Host` header. Version 2.11.1 contains a fix for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-27588</guid>
    </item>
  </channel>
</rss>
