<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T21:35:16.190115+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-33806</id>
    <title>CVE-2026-33806 — fastify vulnerable to Body Schema Validation Bypass via Leading Space in Content-Type Header</title>
    <updated>2026-09-30T21:35:16.193124+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> fastify, Red Hat Enterprise Linux AI (RHEL AI) 3, Red Hat OpenShift AI (RHOAI), Red Hat OpenShift Dev Spaces</p>
<p>Impact:</p>
<p>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.</p>
<p>This is a regression introduced in fastify &gt;= 5.3.2 by the fix for CVE-2025-32442</p>
<p>Patches:</p>
<p>Upgrade to fastify v5.8.5 or later.</p>
<p>Workarounds:</p>
<p>None. Upgrade to the patched version.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-33806"/>
  </entry>
</feed>
