<?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>Sat, 03 Oct 2026 16:06:10 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-09015</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-09015</link>
      <description>bdu:2026-09015</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-09015</guid>
    </item>
    <item>
      <title>EUVD-2026-337330</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-337330</link>
      <description>EUVD-2026-337330</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-337330</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33806</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33806</link>
      <description>&lt;p&gt;Impact:&lt;/p&gt;
&lt;p&gt;Fastify applications using schema.body.content for per-content-type body validation can have validation bypassed entirely by prepending a space to the Content-Type header. The body is still parsed correctly but schema validation is skipped.&lt;/p&gt;
&lt;p&gt;This is a regression introduced in fastify &amp;gt;= 5.3.2 by the fix for CVE-2025-32442&lt;/p&gt;
&lt;p&gt;Patches:&lt;/p&gt;
&lt;p&gt;Upgrade to fastify v5.8.5 or later.&lt;/p&gt;
&lt;p&gt;Workarounds:&lt;/p&gt;
&lt;p&gt;None. Upgrade to the patched version.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Impact:&lt;/p&gt;
&lt;p&gt;Fastify applications using schema.body.content for per-content-type body validation can have validation bypassed entirely by prepending a space to the Content-Type header. The body is still parsed correctly but schema validation is skipped.&lt;/p&gt;
&lt;p&gt;This is a regression introduced in fastify &amp;gt;= 5.3.2 by the fix for CVE-2025-32442&lt;/p&gt;
&lt;p&gt;Patches:&lt;/p&gt;
&lt;p&gt;Upgrade to fastify v5.8.5 or later.&lt;/p&gt;
&lt;p&gt;Workarounds:&lt;/p&gt;
&lt;p&gt;None. Upgrade to the patched version.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-33806</guid>
    </item>
    <item>
      <title>GHSA-247c-9743-5963 — Fastify has a Body Schema Validation Bypass via Leading Space in Content-Type Header</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-247c-9743-5963</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: fastify&lt;/p&gt;
&lt;p&gt;### Summary
A validation bypass vulnerability exists in Fastify v5.x where request body validation schemas specified via `schema.body.content` can be completely circumvented by prepending a single space character (`\x20`) to the `Content-Type` header. The body is still parsed correctly as JSON (or any other content type), but schema validation is entirely skipped.
This is a regression introduced by commit [`f3d2bcb`](https://github.com/fastify/fastify/commit/f3d2bcb3963cd570a582e5d39aab01a9ae692fe4) (fix for [CVE-2025-32442](https://github.com/fastify/fastify/security/advisories/GHSA-mg2h-6x62-wpwc)).&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability is a **parser-validator differential** between two independent code paths that process the raw `Content-Type` header differently.
**Parser path** (`lib/content-type.js`, line ~67) applies `trimStart()` before processing:
```js
const type = headerValue.slice(0, sepIdx).trimStart().toLowerCase()
// &amp;#39; application/json&amp;#39; → trimStart() → &amp;#39;application/json&amp;#39; → body is parsed ✓
```&lt;/p&gt;
&lt;p&gt;**Validator path** (`lib/validation.js`, line 272) splits on `/[ ;]/` before trimming:&lt;/p&gt;
&lt;p&gt;```js
function getEssenceMediaType(header) {
  if (!header) return &amp;#39;&amp;#39;
  return header.split(/[ ;]/, 1)[0].trim().toLowerCase()
}
// &amp;#39; application/json&amp;#39;.split(/[ ;]/, 1) → [&amp;#39;&amp;#39;]  (splits on the leading space!)
// &amp;#39;&amp;#39;.trim() → &amp;#39;&amp;#39;
// context[bodySchema][&amp;#39;&amp;#39;] → undefined → NO validator found → validation skipped!
```&lt;/p&gt;
&lt;p&gt;The `ContentType` class applies `trimStart()` before processing, so the parser co…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: fastify&lt;/p&gt;
&lt;p&gt;### Summary
A validation bypass vulnerability exists in Fastify v5.x where request body validation schemas specified via `schema.body.content` can be completely circumvented by prepending a single space character (`\x20`) to the `Content-Type` header. The body is still parsed correctly as JSON (or any other content type), but schema validation is entirely skipped.
This is a regression introduced by commit [`f3d2bcb`](https://github.com/fastify/fastify/commit/f3d2bcb3963cd570a582e5d39aab01a9ae692fe4) (fix for [CVE-2025-32442](https://github.com/fastify/fastify/security/advisories/GHSA-mg2h-6x62-wpwc)).&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability is a **parser-validator differential** between two independent code paths that process the raw `Content-Type` header differently.
**Parser path** (`lib/content-type.js`, line ~67) applies `trimStart()` before processing:
```js
const type = headerValue.slice(0, sepIdx).trimStart().toLowerCase()
// &amp;#39; application/json&amp;#39; → trimStart() → &amp;#39;application/json&amp;#39; → body is parsed ✓
```&lt;/p&gt;
&lt;p&gt;**Validator path** (`lib/validation.js`, line 272) splits on `/[ ;]/` before trimming:&lt;/p&gt;
&lt;p&gt;```js
function getEssenceMediaType(header) {
  if (!header) return &amp;#39;&amp;#39;
  return header.split(/[ ;]/, 1)[0].trim().toLowerCase()
}
// &amp;#39; application/json&amp;#39;.split(/[ ;]/, 1) → [&amp;#39;&amp;#39;]  (splits on the leading space!)
// &amp;#39;&amp;#39;.trim() → &amp;#39;&amp;#39;
// context[bodySchema][&amp;#39;&amp;#39;] → undefined → NO validator found → validation skipped!
```&lt;/p&gt;
&lt;p&gt;The `ContentType` class applies `trimStart()` before processing, so the parser co…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-247c-9743-5963</guid>
    </item>
  </channel>
</rss>
