<?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>Wed, 07 Oct 2026 02:42:55 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-266016</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-266016</link>
      <description>EUVD-2026-266016</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-266016</guid>
    </item>
    <item>
      <title>fkie_cve-2026-22031</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-22031</link>
      <description>&lt;p&gt;@fastify/middie is the plugin that adds middleware support on steroids to Fastify. A security vulnerability exists in @fastify/middie prior to version 9.1.0 where middleware registered with a specific path prefix can be bypassed using URL-encoded characters (e.g., `/%61dmin` instead of `/admin`). While the middleware engine fails to match the encoded path and skips execution, the underlying Fastify router correctly decodes the path and matches the route handler, allowing attackers to access protected endpoints without the middleware constraints. Version 9.1.0 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;@fastify/middie is the plugin that adds middleware support on steroids to Fastify. A security vulnerability exists in @fastify/middie prior to version 9.1.0 where middleware registered with a specific path prefix can be bypassed using URL-encoded characters (e.g., `/%61dmin` instead of `/admin`). While the middleware engine fails to match the encoded path and skips execution, the underlying Fastify router correctly decodes the path and matches the route handler, allowing attackers to access protected endpoints without the middleware constraints. Version 9.1.0 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-22031</guid>
    </item>
    <item>
      <title>GHSA-cxrg-g7r8-w69p — Fastify Middie Middleware Path Bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cxrg-g7r8-w69p</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @fastify/middie&lt;/p&gt;
&lt;p&gt;### Summary
A security vulnerability exists in `@fastify/middie` where middleware registered with a specific path prefix can be bypassed using URL-encoded characters (e.g., `/%61dmin` instead of `/admin`). While the middleware engine fails to match the encoded path and skips execution, the underlying Fastify router correctly decodes the path and matches the route handler, allowing attackers to access protected endpoints without the middleware constraints.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability is caused by how `middie` matches requests against registered middleware paths.&lt;/p&gt;
&lt;p&gt;1.  **Regex Generation**: When [fastify.use(&amp;#39;/admin&amp;#39;, ...)](cci:1://file:///Users/harshjaiswal/work/research/nest/packages/platform-fastify/adapters/fastify-adapter.ts:733:2-741:3) is called, `middie` uses `path-to-regexp` to generate a regular expression for the path `/admin`.
2.  **Request Matching**: For every request, `middie` executes this regular expression against `req.url` (or `req.originalUrl`).
3.  **The Flaw**: `req.url` in Fastify contains the **raw, undecoded** path string.
    *   The generated regex expects a decoded path (e.g., `/admin`).
    *   If a request is sent to `/%61dmin`, the regex comparison fails (`/^\/admin/` does not match `/%61dmin`).
    *   `middie` assumes the middleware does not apply and calls `next()`.
4.  **Route Execution**: The request proceeds to Fastify&amp;#39;s internal router, which performs URL decoding. It correctly identifies `/%61dmin` as `/admin` and executes the correspon…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @fastify/middie&lt;/p&gt;
&lt;p&gt;### Summary
A security vulnerability exists in `@fastify/middie` where middleware registered with a specific path prefix can be bypassed using URL-encoded characters (e.g., `/%61dmin` instead of `/admin`). While the middleware engine fails to match the encoded path and skips execution, the underlying Fastify router correctly decodes the path and matches the route handler, allowing attackers to access protected endpoints without the middleware constraints.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability is caused by how `middie` matches requests against registered middleware paths.&lt;/p&gt;
&lt;p&gt;1.  **Regex Generation**: When [fastify.use(&amp;#39;/admin&amp;#39;, ...)](cci:1://file:///Users/harshjaiswal/work/research/nest/packages/platform-fastify/adapters/fastify-adapter.ts:733:2-741:3) is called, `middie` uses `path-to-regexp` to generate a regular expression for the path `/admin`.
2.  **Request Matching**: For every request, `middie` executes this regular expression against `req.url` (or `req.originalUrl`).
3.  **The Flaw**: `req.url` in Fastify contains the **raw, undecoded** path string.
    *   The generated regex expects a decoded path (e.g., `/admin`).
    *   If a request is sent to `/%61dmin`, the regex comparison fails (`/^\/admin/` does not match `/%61dmin`).
    *   `middie` assumes the middleware does not apply and calls `next()`.
4.  **Route Execution**: The request proceeds to Fastify&amp;#39;s internal router, which performs URL decoding. It correctly identifies `/%61dmin` as `/admin` and executes the correspon…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cxrg-g7r8-w69p</guid>
    </item>
  </channel>
</rss>
