<?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>Fri, 02 Oct 2026 10:45:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-25965 — ImageMagick's policy bypass through path traversal allows reading restricted content despite secured policy</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-25965</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ImageMagick, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 6&lt;/p&gt;
&lt;p&gt;ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2-15 and 6.9.13-40, ImageMagick’s path security policy is enforced on the raw filename string before the filesystem resolves it. As a result, a policy rule such as /etc/* can be bypassed by a path traversal. The OS resolves the traversal and opens the sensitive file, but the policy matcher only sees the unnormalized path and therefore allows the read. This enables local file disclosure (LFI) even when policy-secure.xml is applied. Actions to prevent reading from files have been taken in versions .7.1.2-15 and 6.9.13-40 But it make sure writing is also not possible the following should be added to one&amp;#39;s policy. This will also be included in ImageMagick&amp;#39;s more secure policies by default.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ImageMagick, Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 6&lt;/p&gt;
&lt;p&gt;ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2-15 and 6.9.13-40, ImageMagick’s path security policy is enforced on the raw filename string before the filesystem resolves it. As a result, a policy rule such as /etc/* can be bypassed by a path traversal. The OS resolves the traversal and opens the sensitive file, but the policy matcher only sees the unnormalized path and therefore allows the read. This enables local file disclosure (LFI) even when policy-secure.xml is applied. Actions to prevent reading from files have been taken in versions .7.1.2-15 and 6.9.13-40 But it make sure writing is also not possible the following should be added to one&amp;#39;s policy. This will also be included in ImageMagick&amp;#39;s more secure policies by default.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-25965</guid>
    </item>
  </channel>
</rss>
