<?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>Tue, 06 Oct 2026 14:43:19 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-336144</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-336144</link>
      <description>EUVD-2026-336144</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-336144</guid>
    </item>
    <item>
      <title>fkie_cve-2026-55466</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-55466</link>
      <description>&lt;p&gt;Snipe-IT is an IT asset/license management system. Prior to 8.6.2, UploadFileRequest sanitizes SVG content only when PHP finfo reports image/svg+xml and UploadedFilesController serves attachments inline without using StorageHelper::allowSafeInline(), allowing a low-privilege user to upload active XHTML or XML content that is later served same-origin and executes JavaScript in a viewer’s browser. This issue is fixed in version 8.6.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Snipe-IT is an IT asset/license management system. Prior to 8.6.2, UploadFileRequest sanitizes SVG content only when PHP finfo reports image/svg+xml and UploadedFilesController serves attachments inline without using StorageHelper::allowSafeInline(), allowing a low-privilege user to upload active XHTML or XML content that is later served same-origin and executes JavaScript in a viewer’s browser. This issue is fixed in version 8.6.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-55466</guid>
    </item>
    <item>
      <title>GHSA-jhph-5q74-pmfx — Snipe-IT vulnerable to stored XSS via inline-served attachment</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jhph-5q74-pmfx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: snipe/snipe-it&lt;/p&gt;
&lt;p&gt;### Impact
A low-privilege user can store an active-content payload as an asset attachment and have it served inline, same-origin, with an active Content-Type, achieving stored XSS. The application sanitizes uploads only when PHP finfo detects image/svg+xml. By submitting an XHTML document whose finfo MIME is text/xml (an allowed extension), the svg-sanitize branch is skipped, the &amp;lt;script&amp;gt; is stored raw, and the inline-serve path returns it as text/xml; charset=utf-8 with Content-Disposition: inline — which the browser renders as a live XHTML document and executes. The dedicated StorageHelper::allowSafeInline() whitelist that should have constrained inline-renderable types is never wired into the serve path.&lt;/p&gt;
&lt;p&gt;### Details
Vulnerable code — sanitizer keyed on finfo MIME `app/Http/Requests/UploadFileRequest.php:46-53`&lt;/p&gt;
&lt;p&gt;```php
$extension = $file-&amp;gt;getClientOriginalExtension();
$file_name = $name_prefix.&amp;#39;-&amp;#39;.str_random(8).&amp;#39;-&amp;#39;.str_slug(...).&amp;#39;.&amp;#39;.$file-&amp;gt;guessExtension();
...
if ($file-&amp;gt;getMimeType() === &amp;#39;image/svg+xml&amp;#39;) {
    $uploaded_file = $this-&amp;gt;handleSVG($file);   // svg-sanitize fires
} else {
    $uploaded_file = file_get_contents($file);   // stored RAW — no sanitization
}
```&lt;/p&gt;
&lt;p&gt;Vulnerable code — inline serve, no `allowSafeInline()` `app/Http/Controllers/UploadedFilesController.php:103`&lt;/p&gt;
&lt;p&gt;```php
if (request(&amp;#39;inline&amp;#39;) == &amp;#39;true&amp;#39;) {
    $headers = [&amp;#39;Content-Disposition&amp;#39; =&amp;gt; &amp;#39;inline&amp;#39;];
    return Storage::download($path.$log-&amp;gt;filename, $log-&amp;gt;filename, $headers);
}
```&lt;/p&gt;
&lt;p&gt;`StorageHelper…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: snipe/snipe-it&lt;/p&gt;
&lt;p&gt;### Impact
A low-privilege user can store an active-content payload as an asset attachment and have it served inline, same-origin, with an active Content-Type, achieving stored XSS. The application sanitizes uploads only when PHP finfo detects image/svg+xml. By submitting an XHTML document whose finfo MIME is text/xml (an allowed extension), the svg-sanitize branch is skipped, the &amp;lt;script&amp;gt; is stored raw, and the inline-serve path returns it as text/xml; charset=utf-8 with Content-Disposition: inline — which the browser renders as a live XHTML document and executes. The dedicated StorageHelper::allowSafeInline() whitelist that should have constrained inline-renderable types is never wired into the serve path.&lt;/p&gt;
&lt;p&gt;### Details
Vulnerable code — sanitizer keyed on finfo MIME `app/Http/Requests/UploadFileRequest.php:46-53`&lt;/p&gt;
&lt;p&gt;```php
$extension = $file-&amp;gt;getClientOriginalExtension();
$file_name = $name_prefix.&amp;#39;-&amp;#39;.str_random(8).&amp;#39;-&amp;#39;.str_slug(...).&amp;#39;.&amp;#39;.$file-&amp;gt;guessExtension();
...
if ($file-&amp;gt;getMimeType() === &amp;#39;image/svg+xml&amp;#39;) {
    $uploaded_file = $this-&amp;gt;handleSVG($file);   // svg-sanitize fires
} else {
    $uploaded_file = file_get_contents($file);   // stored RAW — no sanitization
}
```&lt;/p&gt;
&lt;p&gt;Vulnerable code — inline serve, no `allowSafeInline()` `app/Http/Controllers/UploadedFilesController.php:103`&lt;/p&gt;
&lt;p&gt;```php
if (request(&amp;#39;inline&amp;#39;) == &amp;#39;true&amp;#39;) {
    $headers = [&amp;#39;Content-Disposition&amp;#39; =&amp;gt; &amp;#39;inline&amp;#39;];
    return Storage::download($path.$log-&amp;gt;filename, $log-&amp;gt;filename, $headers);
}
```&lt;/p&gt;
&lt;p&gt;`StorageHelper…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jhph-5q74-pmfx</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2073 — Snipe-IT: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2073</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Snipe-IT ausnutzen, um Dateien zu manipulieren, um Sicherheitsvorkehrungen zu umgehen, um einen Cross-Site Scripting Angriff durchzuführen und um beliebigen Programmcode auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Snipe-IT ausnutzen, um Dateien zu manipulieren, um Sicherheitsvorkehrungen zu umgehen, um einen Cross-Site Scripting Angriff durchzuführen und um beliebigen Programmcode auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2073</guid>
    </item>
  </channel>
</rss>
