<?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>Wed, 30 Sep 2026 13:37:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-47725 — nebula-mesh: Web UI lacks CSRF tokens on /ui/* mutating endpoints</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-47725</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.3, every /ui/* POST / PUT / PATCH / DELETE route processes the request as soon as the session cookie validates. SameSite=Lax on the session cookie prevents most cross-site form submits but does not protect: top-level form-submit navigations from third-party pages (some browsers still send Lax cookies on top-level POSTs); same-registrable-domain attackers (sibling-subdomain XSS, subdomain takeover); the GET /ui/logout route, which a third-party &amp;lt;img src=&amp;#34;.../ui/logout&amp;#34;&amp;gt; can force-trigger. This issue has been patched in version 0.3.3.&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.3, every /ui/* POST / PUT / PATCH / DELETE route processes the request as soon as the session cookie validates. SameSite=Lax on the session cookie prevents most cross-site form submits but does not protect: top-level form-submit navigations from third-party pages (some browsers still send Lax cookies on top-level POSTs); same-registrable-domain attackers (sibling-subdomain XSS, subdomain takeover); the GET /ui/logout route, which a third-party &amp;lt;img src=&amp;#34;.../ui/logout&amp;#34;&amp;gt; can force-trigger. This issue has been patched in version 0.3.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-47725</guid>
    </item>
  </channel>
</rss>
