<?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 03:39:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-32792 — ses's global contour bindings leak into Compartment lexical scope</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-32792</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; endojs endo&lt;/p&gt;
&lt;p&gt;SES safely executes third-party JavaScript &amp;#39;strict&amp;#39; mode programs in compartments that have no excess authority in their global scope. Prior to version 1.12.0, web pages and web extensions using `ses` and the Compartment API to evaluate third-party code in an isolated execution environment that have also elsewhere used `const`, `let`, and `class` bindings in the top-level scope of a `&amp;lt;script&amp;gt;` tag will have inadvertently revealed these bindings in the lexical scope of third-party code. This issue has been patched in version 1.12.0. Workarounds for this issue involve either avoiding top-level `let`, `const`, or `class` bindings in `&amp;lt;script&amp;gt;` tags, or change these to `var` bindings to be reflected on `globalThis`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; endojs endo&lt;/p&gt;
&lt;p&gt;SES safely executes third-party JavaScript &amp;#39;strict&amp;#39; mode programs in compartments that have no excess authority in their global scope. Prior to version 1.12.0, web pages and web extensions using `ses` and the Compartment API to evaluate third-party code in an isolated execution environment that have also elsewhere used `const`, `let`, and `class` bindings in the top-level scope of a `&amp;lt;script&amp;gt;` tag will have inadvertently revealed these bindings in the lexical scope of third-party code. This issue has been patched in version 1.12.0. Workarounds for this issue involve either avoiding top-level `let`, `const`, or `class` bindings in `&amp;lt;script&amp;gt;` tags, or change these to `var` bindings to be reflected on `globalThis`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-32792</guid>
    </item>
  </channel>
</rss>
