<?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>Thu, 08 Oct 2026 10:20:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-65600 — Traefik before v2.11.52 Authentication Bypass via ReplacePathRegex</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-65600</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; traefik&lt;/p&gt;
&lt;p&gt;Traefik versions &amp;lt;= v2.11.51, &amp;gt;= v3.6.0 &amp;lt;= v3.6.22, and &amp;gt;= v3.7.0 &amp;lt;= v3.7.6 contain an authentication bypass via path traversal in the ReplacePathRegex middleware. When ReplacePathRegex is configured with a regex that captures user-controlled path segments without a mandatory path separator (e.g. regex &amp;#34;^/api(.*)&amp;#34;, replacement &amp;#34;/$1&amp;#34;), the middleware forwards the replaced path to the backend without validating that it matches its normalized form. An unauthenticated remote attacker can send a crafted request (e.g. GET /api../admin) that produces an un-normalized path such as /../admin, which a backend that normalizes paths resolves to a protected route, bypassing authentication middleware. Fixed in v2.11.52, v3.6.23, and v3.7.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; traefik&lt;/p&gt;
&lt;p&gt;Traefik versions &amp;lt;= v2.11.51, &amp;gt;= v3.6.0 &amp;lt;= v3.6.22, and &amp;gt;= v3.7.0 &amp;lt;= v3.7.6 contain an authentication bypass via path traversal in the ReplacePathRegex middleware. When ReplacePathRegex is configured with a regex that captures user-controlled path segments without a mandatory path separator (e.g. regex &amp;#34;^/api(.*)&amp;#34;, replacement &amp;#34;/$1&amp;#34;), the middleware forwards the replaced path to the backend without validating that it matches its normalized form. An unauthenticated remote attacker can send a crafted request (e.g. GET /api../admin) that produces an un-normalized path such as /../admin, which a backend that normalizes paths resolves to a protected route, bypassing authentication middleware. Fixed in v2.11.52, v3.6.23, and v3.7.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-65600</guid>
    </item>
  </channel>
</rss>
