<?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>Thu, 08 Oct 2026 06:39:43 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-193936</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-193936</link>
      <description>EUVD-2026-193936</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-193936</guid>
    </item>
    <item>
      <title>fkie_cve-2024-45291</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-45291</link>
      <description>&lt;p&gt;PHPSpreadsheet is a pure PHP library for reading and writing spreadsheet files. It&amp;#39;s possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer-&amp;gt;setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file&amp;#39;s type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability. When embedding images has been enabled, an attacker can read arbitrary files on the server and perform arbitrary HTTP GET requests. Note that any PHP protocol wrappers can be used, meaning that if for example the `expect://` wrapper is enabled, also remote code execution is possible. This issue has been addressed in release versions 1.29.2, 2.1.1, and 2.3.0. All users are advised to upgrade. there are no known workarounds for this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;PHPSpreadsheet is a pure PHP library for reading and writing spreadsheet files. It&amp;#39;s possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer-&amp;gt;setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file&amp;#39;s type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability. When embedding images has been enabled, an attacker can read arbitrary files on the server and perform arbitrary HTTP GET requests. Note that any PHP protocol wrappers can be used, meaning that if for example the `expect://` wrapper is enabled, also remote code execution is possible. This issue has been addressed in release versions 1.29.2, 2.1.1, and 2.3.0. All users are advised to upgrade. there are no known workarounds for this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-45291</guid>
    </item>
    <item>
      <title>GHSA-w9xv-qf98-ccq4 — PhpSpreadsheet allows absolute path traversal and Server-Side Request Forgery in HTML writer when embedding images is e…</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w9xv-qf98-ccq4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: phpoffice/phpspreadsheet, Packagist: phpoffice/phpexcel&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;It&amp;#39;s possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer-&amp;gt;setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file&amp;#39;s type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;XLSX files allow embedding or linking media. When&lt;/p&gt;
&lt;p&gt;In `xl/drawings/drawing1.xml` an attacker can do e.g.:
```xml
&amp;lt;a:blip cstate=&amp;#34;print&amp;#34; r:link=&amp;#34;rId1&amp;#34; /&amp;gt;
```&lt;/p&gt;
&lt;p&gt;And then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:
```xml
&amp;lt;Relationship Id=&amp;#34;rId1&amp;#34;
    Type=&amp;#34;http://schemas.openxmlformats.org/officeDocument/2006/relationships/image&amp;#34;
    Target=&amp;#34;/etc/passwd&amp;#34; /&amp;gt;
```
or
```xml
&amp;lt;Relationship Id=&amp;#34;rId1&amp;#34;
    Type=&amp;#34;http://schemas.openxmlformats.org/officeDocument/2006/relationships/image&amp;#34;
    Target=&amp;#34;http://example.org&amp;#34; /&amp;gt;
```&lt;/p&gt;
&lt;p&gt;When the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.&lt;/p&gt;
&lt;p&gt;```php
if ($this-&amp;gt;embedImages || str_starts_with($imageData, &amp;#39;zip://&amp;#39;)) {
    $picture = @file_get_contents($filename);
    if ($picture !== false) {
        $imageDetails = getimagesize($filename) ?: [&amp;#39;mime&amp;#39; =&amp;gt; &amp;#39;&amp;#39;];
        // base64 encode the binary data
        $base64 = base64_encode($picture);
        $imageData = &amp;#39;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: phpoffice/phpspreadsheet, Packagist: phpoffice/phpexcel&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;It&amp;#39;s possible for an attacker to construct an XLSX file that links images from arbitrary paths. When embedding images has been enabled in HTML writer with `$writer-&amp;gt;setEmbedImages(true);` those files will be included in the output as `data:` URLs, regardless of the file&amp;#39;s type. Also URLs can be used for embedding, resulting in a Server-Side Request Forgery vulnerability.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;XLSX files allow embedding or linking media. When&lt;/p&gt;
&lt;p&gt;In `xl/drawings/drawing1.xml` an attacker can do e.g.:
```xml
&amp;lt;a:blip cstate=&amp;#34;print&amp;#34; r:link=&amp;#34;rId1&amp;#34; /&amp;gt;
```&lt;/p&gt;
&lt;p&gt;And then, in `xl/drawings/_rels/drawing1.xml.rels` they can set the path to anything, such as:
```xml
&amp;lt;Relationship Id=&amp;#34;rId1&amp;#34;
    Type=&amp;#34;http://schemas.openxmlformats.org/officeDocument/2006/relationships/image&amp;#34;
    Target=&amp;#34;/etc/passwd&amp;#34; /&amp;gt;
```
or
```xml
&amp;lt;Relationship Id=&amp;#34;rId1&amp;#34;
    Type=&amp;#34;http://schemas.openxmlformats.org/officeDocument/2006/relationships/image&amp;#34;
    Target=&amp;#34;http://example.org&amp;#34; /&amp;gt;
```&lt;/p&gt;
&lt;p&gt;When the HTML writer is outputting the image, it does not check the path in any way. Also the `getimagesize()` call does not mitigate this, because when `getimagesize()` returns false, an empty mime type is used.&lt;/p&gt;
&lt;p&gt;```php
if ($this-&amp;gt;embedImages || str_starts_with($imageData, &amp;#39;zip://&amp;#39;)) {
    $picture = @file_get_contents($filename);
    if ($picture !== false) {
        $imageDetails = getimagesize($filename) ?: [&amp;#39;mime&amp;#39; =&amp;gt; &amp;#39;&amp;#39;];
        // base64 encode the binary data
        $base64 = base64_encode($picture);
        $imageData = &amp;#39;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w9xv-qf98-ccq4</guid>
    </item>
  </channel>
</rss>
