<?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://vulnerability.circl.lu</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, 29 Sep 2026 03:51:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-22775 — devalue vulnerable to denial of service due to memory/CPU exhaustion in devalue.parse</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-22775</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; sveltejs devalue, Red Hat Trusted Artifact Signer 1.2, Red Hat Trusted Artifact Signer 1.3, Red Hat Build of Podman Desktop - Tech Preview&lt;/p&gt;
&lt;p&gt;Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn&amp;#39;t sufficient for the job. From 5.1.0 to 5.6.1, certain inputs can cause devalue.parse to consume excessive CPU time and/or memory, potentially leading to denial of service in systems that parse input from untrusted sources. This affects applications using devalue.parse on externally-supplied data. The root cause is the ArrayBuffer hydration expecting base64 encoded strings as input, but not checking the assumption before decoding the input. This vulnerability is fixed in 5.6.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; sveltejs devalue, Red Hat Trusted Artifact Signer 1.2, Red Hat Trusted Artifact Signer 1.3, Red Hat Build of Podman Desktop - Tech Preview&lt;/p&gt;
&lt;p&gt;Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn&amp;#39;t sufficient for the job. From 5.1.0 to 5.6.1, certain inputs can cause devalue.parse to consume excessive CPU time and/or memory, potentially leading to denial of service in systems that parse input from untrusted sources. This affects applications using devalue.parse on externally-supplied data. The root cause is the ArrayBuffer hydration expecting base64 encoded strings as input, but not checking the assumption before decoding the input. This vulnerability is fixed in 5.6.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-22775</guid>
    </item>
  </channel>
</rss>
