<?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>Sun, 04 Oct 2026 16:25:49 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-14935</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2026-14935</link>
      <description>bdu:2026-14935</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2026-14935</guid>
    </item>
    <item>
      <title>CVE-2026-92940 — vm2 3.11.3 through 3.11.6 HTTPS Credential Exposure via globalAgent</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-92940</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; patriksimek vm2&lt;/p&gt;
&lt;p&gt;vm2 versions 3.11.3 through 3.11.6 expose the host process&amp;#39;s real https.globalAgent to sandboxed code when a NodeVM is explicitly configured to allow require(&amp;#39;https&amp;#39;). The builtin loader wraps host modules in a read-only proxy, but method calls such as Agent.prototype.on() are forwarded to the underlying host object, so sandbox code can register a listener for the agent&amp;#39;s &amp;#39;free&amp;#39; event. When an unrelated host HTTPS request releases a pooled connection, the listener receives the live host request options and the host TLSSocket, allowing sandboxed code to read the host&amp;#39;s Authorization header and private destination host/port, attach a data listener to the released socket and read subsequent host response bodies in plaintext, and issue attacker-chosen authenticated requests using the stolen credentials. The issue is fixed in 3.11.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; patriksimek vm2&lt;/p&gt;
&lt;p&gt;vm2 versions 3.11.3 through 3.11.6 expose the host process&amp;#39;s real https.globalAgent to sandboxed code when a NodeVM is explicitly configured to allow require(&amp;#39;https&amp;#39;). The builtin loader wraps host modules in a read-only proxy, but method calls such as Agent.prototype.on() are forwarded to the underlying host object, so sandbox code can register a listener for the agent&amp;#39;s &amp;#39;free&amp;#39; event. When an unrelated host HTTPS request releases a pooled connection, the listener receives the live host request options and the host TLSSocket, allowing sandboxed code to read the host&amp;#39;s Authorization header and private destination host/port, attach a data listener to the released socket and read subsequent host response bodies in plaintext, and issue attacker-chosen authenticated requests using the stolen credentials. The issue is fixed in 3.11.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-92940</guid>
    </item>
  </channel>
</rss>
