<?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>Sun, 04 Oct 2026 10:16:43 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-255253</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-255253</link>
      <description>EUVD-2026-255253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-255253</guid>
    </item>
    <item>
      <title>fkie_cve-2025-62491</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-62491</link>
      <description>&lt;p&gt;A Use-After-Free (UAF) vulnerability exists in the QuickJS engine&amp;#39;s standard library when iterating over the global list of unhandled rejected promises (ts-&amp;gt;rejected_promise_list).&lt;/p&gt;
&lt;p&gt;*  The function js_std_promise_rejection_check attempts to iterate over the rejected_promise_list to report unhandled rejections using a standard list loop.&lt;/p&gt;
&lt;p&gt;*  The reason for a promise rejection is processed inside the loop, including calling js_std_dump_error1(ctx, rp-&amp;gt;reason).&lt;/p&gt;
&lt;p&gt;*  If the promise rejection reason is an Error object that defines a custom property getter (e.g., via Object.defineProperty), this getter is executed during the error dumping process.&lt;/p&gt;
&lt;p&gt;*  The malicious custom getter can execute JavaScript code that calls catch() on the same rejected promise being processed.&lt;/p&gt;
&lt;p&gt;*  Calling catch() internally triggers js_std_promise_rejection_tracker, which then removes and frees the current promise entry (JSRejectedPromiseEntry) from the rejected_promise_list.&lt;/p&gt;
&lt;p&gt;*  Since the list iteration continues using the now-freed memory pointer (el), the subsequent loop access results in a Use-After-Free condition.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A Use-After-Free (UAF) vulnerability exists in the QuickJS engine&amp;#39;s standard library when iterating over the global list of unhandled rejected promises (ts-&amp;gt;rejected_promise_list).&lt;/p&gt;
&lt;p&gt;*  The function js_std_promise_rejection_check attempts to iterate over the rejected_promise_list to report unhandled rejections using a standard list loop.&lt;/p&gt;
&lt;p&gt;*  The reason for a promise rejection is processed inside the loop, including calling js_std_dump_error1(ctx, rp-&amp;gt;reason).&lt;/p&gt;
&lt;p&gt;*  If the promise rejection reason is an Error object that defines a custom property getter (e.g., via Object.defineProperty), this getter is executed during the error dumping process.&lt;/p&gt;
&lt;p&gt;*  The malicious custom getter can execute JavaScript code that calls catch() on the same rejected promise being processed.&lt;/p&gt;
&lt;p&gt;*  Calling catch() internally triggers js_std_promise_rejection_tracker, which then removes and frees the current promise entry (JSRejectedPromiseEntry) from the rejected_promise_list.&lt;/p&gt;
&lt;p&gt;*  Since the list iteration continues using the now-freed memory pointer (el), the subsequent loop access results in a Use-After-Free condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-62491</guid>
    </item>
    <item>
      <title>GHSA-3r39-xffq-r9cc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3r39-xffq-r9cc</link>
      <description>&lt;p&gt;A Use-After-Free (UAF) vulnerability exists in the QuickJS engine&amp;#39;s standard library when iterating over the global list of unhandled rejected promises (ts-&amp;gt;rejected_promise_list).&lt;/p&gt;
&lt;p&gt;*  The function js_std_promise_rejection_check attempts to iterate over the rejected_promise_list to report unhandled rejections using a standard list loop.&lt;/p&gt;
&lt;p&gt;*  The reason for a promise rejection is processed inside the loop, including calling js_std_dump_error1(ctx, rp-&amp;gt;reason).&lt;/p&gt;
&lt;p&gt;*  If the promise rejection reason is an Error object that defines a custom property getter (e.g., via Object.defineProperty), this getter is executed during the error dumping process.&lt;/p&gt;
&lt;p&gt;*  The malicious custom getter can execute JavaScript code that calls catch() on the same rejected promise being processed.&lt;/p&gt;
&lt;p&gt;*  Calling catch() internally triggers js_std_promise_rejection_tracker, which then removes and frees the current promise entry (JSRejectedPromiseEntry) from the rejected_promise_list.&lt;/p&gt;
&lt;p&gt;*  Since the list iteration continues using the now-freed memory pointer (el), the subsequent loop access results in a Use-After-Free condition.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A Use-After-Free (UAF) vulnerability exists in the QuickJS engine&amp;#39;s standard library when iterating over the global list of unhandled rejected promises (ts-&amp;gt;rejected_promise_list).&lt;/p&gt;
&lt;p&gt;*  The function js_std_promise_rejection_check attempts to iterate over the rejected_promise_list to report unhandled rejections using a standard list loop.&lt;/p&gt;
&lt;p&gt;*  The reason for a promise rejection is processed inside the loop, including calling js_std_dump_error1(ctx, rp-&amp;gt;reason).&lt;/p&gt;
&lt;p&gt;*  If the promise rejection reason is an Error object that defines a custom property getter (e.g., via Object.defineProperty), this getter is executed during the error dumping process.&lt;/p&gt;
&lt;p&gt;*  The malicious custom getter can execute JavaScript code that calls catch() on the same rejected promise being processed.&lt;/p&gt;
&lt;p&gt;*  Calling catch() internally triggers js_std_promise_rejection_tracker, which then removes and frees the current promise entry (JSRejectedPromiseEntry) from the rejected_promise_list.&lt;/p&gt;
&lt;p&gt;*  Since the list iteration continues using the now-freed memory pointer (el), the subsequent loop access results in a Use-After-Free condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3r39-xffq-r9cc</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-62491</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-62491</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:24.04:LTS: quickjs, Ubuntu:25.10: quickjs, Ubuntu:26.04:LTS: quickjs&lt;/p&gt;
&lt;p&gt;A Use-After-Free (UAF) vulnerability exists in the QuickJS engine&amp;#39;s standard library when iterating over the global list of unhandled rejected promises (ts-&amp;gt;rejected_promise_list).   *  The function js_std_promise_rejection_check attempts to iterate over the rejected_promise_list to report unhandled rejections using a standard list loop.   *  The reason for a promise rejection is processed inside the loop, including calling js_std_dump_error1(ctx, rp-&amp;gt;reason).   *  If the promise rejection reason is an Error object that defines a custom property getter (e.g., via Object.defineProperty), this getter is executed during the error dumping process.   *  The malicious custom getter can execute JavaScript code that calls catch() on the same rejected promise being processed.   *  Calling catch() internally triggers js_std_promise_rejection_tracker, which then removes and frees the current promise entry (JSRejectedPromiseEntry) from the rejected_promise_list.   *  Since the list iteration continues using the now-freed memory pointer (el), the subsequent loop access results in a Use-After-Free condition.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:24.04:LTS: quickjs, Ubuntu:25.10: quickjs, Ubuntu:26.04:LTS: quickjs&lt;/p&gt;
&lt;p&gt;A Use-After-Free (UAF) vulnerability exists in the QuickJS engine&amp;#39;s standard library when iterating over the global list of unhandled rejected promises (ts-&amp;gt;rejected_promise_list).   *  The function js_std_promise_rejection_check attempts to iterate over the rejected_promise_list to report unhandled rejections using a standard list loop.   *  The reason for a promise rejection is processed inside the loop, including calling js_std_dump_error1(ctx, rp-&amp;gt;reason).   *  If the promise rejection reason is an Error object that defines a custom property getter (e.g., via Object.defineProperty), this getter is executed during the error dumping process.   *  The malicious custom getter can execute JavaScript code that calls catch() on the same rejected promise being processed.   *  Calling catch() internally triggers js_std_promise_rejection_tracker, which then removes and frees the current promise entry (JSRejectedPromiseEntry) from the rejected_promise_list.   *  Since the list iteration continues using the now-freed memory pointer (el), the subsequent loop access results in a Use-After-Free condition.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-62491</guid>
    </item>
  </channel>
</rss>
