<?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 17:45:40 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-318630</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-318630</link>
      <description>EUVD-2026-318630</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-318630</guid>
    </item>
    <item>
      <title>fkie_cve-2026-22707</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-22707</link>
      <description>&lt;p&gt;Strapi is an open source headless content management system. In Strapi versions prior to 5.33.3, the Upload plugin&amp;#39;s Content API endpoints did not enforce the administrator-configured MIME type restrictions (`plugin.upload.security.allowedTypes` and `deniedTypes`). The same restrictions were correctly enforced on the Admin Panel upload path. The upload plugin&amp;#39;s `enforceUploadSecurity` security check was invoked in the admin upload controller but was missing from the Content API controller. The Content API handlers `uploadFiles` and `replaceFile` (and the `upload` wrapper that dispatches to them) called the underlying upload service directly, bypassing both the magic-byte MIME detection and the configured allow/deny lists. An authenticated user with the Content API upload permission could therefore upload file types the administrator had explicitly disallowed, including HTML and SVG content. In deployments serving uploaded files from the same origin as the admin panel (default), an attacker could upload an HTML or SVG file that, when opened directly by an admin, executed JavaScript in the admin origin, enabling admin-session hijack and authenticated administrative actions against the admin API. The patch in version 5.33.3 introduces a shared `prepareUploadRequest` helper that wraps `enforceUploadSecurity` and is called from both the Content API and admin upload controllers, ensuring identical security policy enforcement on every upload entry point.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Strapi is an open source headless content management system. In Strapi versions prior to 5.33.3, the Upload plugin&amp;#39;s Content API endpoints did not enforce the administrator-configured MIME type restrictions (`plugin.upload.security.allowedTypes` and `deniedTypes`). The same restrictions were correctly enforced on the Admin Panel upload path. The upload plugin&amp;#39;s `enforceUploadSecurity` security check was invoked in the admin upload controller but was missing from the Content API controller. The Content API handlers `uploadFiles` and `replaceFile` (and the `upload` wrapper that dispatches to them) called the underlying upload service directly, bypassing both the magic-byte MIME detection and the configured allow/deny lists. An authenticated user with the Content API upload permission could therefore upload file types the administrator had explicitly disallowed, including HTML and SVG content. In deployments serving uploaded files from the same origin as the admin panel (default), an attacker could upload an HTML or SVG file that, when opened directly by an admin, executed JavaScript in the admin origin, enabling admin-session hijack and authenticated administrative actions against the admin API. The patch in version 5.33.3 introduces a shared `prepareUploadRequest` helper that wraps `enforceUploadSecurity` and is called from both the Content API and admin upload controllers, ensuring identical security policy enforcement on every upload entry point.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-22707</guid>
    </item>
    <item>
      <title>GHSA-pcw7-5633-82vv — Strapi Upload Plugin MIME Validation Bypass via Content API</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pcw7-5633-82vv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @strapi/upload&lt;/p&gt;
&lt;p&gt;### Summary of CVE-2026-22707 Vulnerability Details&lt;/p&gt;
&lt;p&gt;- CVE: CVE-2026-22707
- CVSS v3.1 Vector: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N` (5.3 — Medium)
- Affected Versions: `@strapi/upload` &amp;lt;=5.33.2
- How to Patch: Immediately update your Strapi to &amp;gt;=5.33.3&lt;/p&gt;
&lt;p&gt;### Description of CVE-2026-22707&lt;/p&gt;
&lt;p&gt;In Strapi versions prior to 5.33.3, the Upload plugin&amp;#39;s Content API endpoints did not enforce the administrator-configured MIME type restrictions (`plugin.upload.security.allowedTypes` and `deniedTypes`). The same restrictions were correctly enforced on the Admin Panel upload path.&lt;/p&gt;
&lt;p&gt;The upload plugin&amp;#39;s `enforceUploadSecurity` security check was invoked in the admin upload controller but was missing from the Content API controller. The Content API handlers `uploadFiles` and `replaceFile` (and the `upload` wrapper that dispatches to them) called the underlying upload service directly, bypassing both the magic-byte MIME detection and the configured allow/deny lists.&lt;/p&gt;
&lt;p&gt;An authenticated user with the Content API upload permission could therefore upload file types the administrator had explicitly disallowed, including HTML and SVG content. In deployments serving uploaded files from the same origin as the admin panel (default), an attacker could upload an HTML or SVG file that, when opened directly by an admin, executed JavaScript in the admin origin, enabling admin-session hijack and authenticated administrative actions against the admin API.&lt;/p&gt;
&lt;p&gt;The patch introduces a sha…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @strapi/upload&lt;/p&gt;
&lt;p&gt;### Summary of CVE-2026-22707 Vulnerability Details&lt;/p&gt;
&lt;p&gt;- CVE: CVE-2026-22707
- CVSS v3.1 Vector: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N` (5.3 — Medium)
- Affected Versions: `@strapi/upload` &amp;lt;=5.33.2
- How to Patch: Immediately update your Strapi to &amp;gt;=5.33.3&lt;/p&gt;
&lt;p&gt;### Description of CVE-2026-22707&lt;/p&gt;
&lt;p&gt;In Strapi versions prior to 5.33.3, the Upload plugin&amp;#39;s Content API endpoints did not enforce the administrator-configured MIME type restrictions (`plugin.upload.security.allowedTypes` and `deniedTypes`). The same restrictions were correctly enforced on the Admin Panel upload path.&lt;/p&gt;
&lt;p&gt;The upload plugin&amp;#39;s `enforceUploadSecurity` security check was invoked in the admin upload controller but was missing from the Content API controller. The Content API handlers `uploadFiles` and `replaceFile` (and the `upload` wrapper that dispatches to them) called the underlying upload service directly, bypassing both the magic-byte MIME detection and the configured allow/deny lists.&lt;/p&gt;
&lt;p&gt;An authenticated user with the Content API upload permission could therefore upload file types the administrator had explicitly disallowed, including HTML and SVG content. In deployments serving uploaded files from the same origin as the admin panel (default), an attacker could upload an HTML or SVG file that, when opened directly by an admin, executed JavaScript in the admin origin, enabling admin-session hijack and authenticated administrative actions against the admin API.&lt;/p&gt;
&lt;p&gt;The patch introduces a sha…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pcw7-5633-82vv</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1552 — Strapi: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1552</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Strapi ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen, Administratorrechte zu erlangen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Strapi ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen, Administratorrechte zu erlangen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1552</guid>
    </item>
  </channel>
</rss>
