<?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 15:50:08 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-276675</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-276675</link>
      <description>EUVD-2026-276675</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-276675</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33011</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33011</link>
      <description>&lt;p&gt;Nest is a framework for building scalable Node.js server-side applications. In versions 11.1.15 and below, a NestJS application using @nestjs/platform-fastify GET middleware can be bypassed because Fastify automatically redirects HEAD requests to the corresponding GET handlers (if they exist). As a result: middleware will be completely skipped, the HTTP response won&amp;#39;t include a body (since the response is truncated when redirecting a HEAD request to a GET handler), and the actual handler will still be executed. This issue is fixed in version 11.1.16.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nest is a framework for building scalable Node.js server-side applications. In versions 11.1.15 and below, a NestJS application using @nestjs/platform-fastify GET middleware can be bypassed because Fastify automatically redirects HEAD requests to the corresponding GET handlers (if they exist). As a result: middleware will be completely skipped, the HTTP response won&amp;#39;t include a body (since the response is truncated when redirecting a HEAD request to a GET handler), and the actual handler will still be executed. This issue is fixed in version 11.1.16.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-33011</guid>
    </item>
    <item>
      <title>GHSA-wf42-42fg-fg84 — Nest Fastify HEAD Request Middleware Bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wf42-42fg-fg84</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @nestjs/platform-fastify&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;In a NestJS application using `@nestjs/platform-fastify`, GET middleware can be bypassed because Fastify automatically redirects HEAD requests to the corresponding GET handlers (if they exist).&lt;/p&gt;
&lt;p&gt;As a result:&lt;/p&gt;
&lt;p&gt;- Middleware will be completely skipped.
- The HTTP response won&amp;#39;t include a body (since the response is truncated when redirecting a HEAD request to a GET handler).
- The actual handler will still be executed.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in `@nestjs/platform-fastify@11.1.16`&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @nestjs/platform-fastify&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;In a NestJS application using `@nestjs/platform-fastify`, GET middleware can be bypassed because Fastify automatically redirects HEAD requests to the corresponding GET handlers (if they exist).&lt;/p&gt;
&lt;p&gt;As a result:&lt;/p&gt;
&lt;p&gt;- Middleware will be completely skipped.
- The HTTP response won&amp;#39;t include a body (since the response is truncated when redirecting a HEAD request to a GET handler).
- The actual handler will still be executed.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Fixed in `@nestjs/platform-fastify@11.1.16`&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wf42-42fg-fg84</guid>
    </item>
  </channel>
</rss>
