<?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>Mon, 05 Oct 2026 05:49:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-48025 — nebula-mesh: Decrypted CA private key persists in heap after signing</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-48025</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; juev nebula-mesh&lt;/p&gt;
&lt;p&gt;nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.7, internal/pki/resolver.go:36-64 constructs a CAManager with the plaintext ed25519.PrivateKey after unwrapping via the master key; internal/pki/ca.go:13-16 stores it. Callers at internal/api/enroll.go:116, internal/api/updates.go:297, and internal/api/mobile_bundle.go:40 use the manager for one Sign() and drop the reference on function return — but the underlying slice contents are not wiped before release. The keystore package&amp;#39;s contract (internal/keystore/keystore.go doc: &amp;#34;Callers MUST zeroise the returned plaintext DEK as soon as it is no longer needed&amp;#34;) is not met by the CAManager consumer. Decrypted CA private keys persist in process heap until Go&amp;#39;s GC scavenges the underlying slice — minutes to hours under load, indefinitely on idle servers. This issue has been patched in version 0.3.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; juev nebula-mesh&lt;/p&gt;
&lt;p&gt;nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.7, internal/pki/resolver.go:36-64 constructs a CAManager with the plaintext ed25519.PrivateKey after unwrapping via the master key; internal/pki/ca.go:13-16 stores it. Callers at internal/api/enroll.go:116, internal/api/updates.go:297, and internal/api/mobile_bundle.go:40 use the manager for one Sign() and drop the reference on function return — but the underlying slice contents are not wiped before release. The keystore package&amp;#39;s contract (internal/keystore/keystore.go doc: &amp;#34;Callers MUST zeroise the returned plaintext DEK as soon as it is no longer needed&amp;#34;) is not met by the CAManager consumer. Decrypted CA private keys persist in process heap until Go&amp;#39;s GC scavenges the underlying slice — minutes to hours under load, indefinitely on idle servers. This issue has been patched in version 0.3.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-48025</guid>
    </item>
  </channel>
</rss>
