<?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>Mon, 05 Oct 2026 23:10:30 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-342181</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-342181</link>
      <description>EUVD-2026-342181</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-342181</guid>
    </item>
    <item>
      <title>fkie_cve-2026-47768</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47768</link>
      <description>&lt;p&gt;nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.2, newly-minted operator API key exposed in redirect URL (Referer, history, proxy logs). This issue has been patched in version 0.3.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.2, newly-minted operator API key exposed in redirect URL (Referer, history, proxy logs). This issue has been patched in version 0.3.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-47768</guid>
    </item>
    <item>
      <title>GHSA-9pg3-25fq-p6cc — nebula-mesh: Newly-minted operator API key exposed in redirect URL (Referer, history, proxy logs)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9pg3-25fq-p6cc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/juev/nebula-mesh&lt;/p&gt;
&lt;p&gt;`internal/web/operators.go:251` — after `handleOperatorCreateAPIKey` mints a fresh 32-byte bearer token, the redirect points the operator&amp;#39;s browser at:&lt;/p&gt;
&lt;p&gt;/ui/operators/&amp;lt;id&amp;gt;?new_key=&amp;lt;raw-token&amp;gt;&amp;amp;key_name=&amp;lt;name&amp;gt;&lt;/p&gt;
&lt;p&gt;The raw API key ends up:
- in the browser&amp;#39;s URL history
- in the `Referer` header on every cross-origin asset the detail page loads (any third-party SVG/CSS/JS resource the layout pulls in)
- in any reverse-proxy or load-balancer access log on the path (nginx default `combined` log captures the query string)
- in any structured log sink the operator&amp;#39;s local browser-history backup tool ships out&lt;/p&gt;
&lt;p&gt;`Authorization: Bearer &amp;lt;token&amp;gt;` headers go through the same hops without these problems because access logs typically don&amp;#39;t capture request headers and the browser doesn&amp;#39;t replay headers cross-origin.&lt;/p&gt;
&lt;p&gt;Same handler also appends `name` (`r.FormValue(&amp;#34;name&amp;#34;)`) to the query string without `url.QueryEscape`, so an `&amp;amp;` in the operator-supplied key name corrupts query parsing and a `\r\n` in older proxies could split response headers.&lt;/p&gt;
&lt;p&gt;## Affected
All released versions up to v0.3.1.&lt;/p&gt;
&lt;p&gt;## Reproducer
As admin, create an API key via `/ui/operators/&amp;lt;id&amp;gt;/api-keys` (form POST). The 303 Location header carries the raw token in the query string. Open browser DevTools → Network → response headers; or check the reverse-proxy access log; or check the operator-detail page&amp;#39;s `Referer`-emitting fetches.&lt;/p&gt;
&lt;p&gt;## Suggested fix
Stash the raw key in a one-shot server-side flash storage (e.g., a row in `…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/juev/nebula-mesh&lt;/p&gt;
&lt;p&gt;`internal/web/operators.go:251` — after `handleOperatorCreateAPIKey` mints a fresh 32-byte bearer token, the redirect points the operator&amp;#39;s browser at:&lt;/p&gt;
&lt;p&gt;/ui/operators/&amp;lt;id&amp;gt;?new_key=&amp;lt;raw-token&amp;gt;&amp;amp;key_name=&amp;lt;name&amp;gt;&lt;/p&gt;
&lt;p&gt;The raw API key ends up:
- in the browser&amp;#39;s URL history
- in the `Referer` header on every cross-origin asset the detail page loads (any third-party SVG/CSS/JS resource the layout pulls in)
- in any reverse-proxy or load-balancer access log on the path (nginx default `combined` log captures the query string)
- in any structured log sink the operator&amp;#39;s local browser-history backup tool ships out&lt;/p&gt;
&lt;p&gt;`Authorization: Bearer &amp;lt;token&amp;gt;` headers go through the same hops without these problems because access logs typically don&amp;#39;t capture request headers and the browser doesn&amp;#39;t replay headers cross-origin.&lt;/p&gt;
&lt;p&gt;Same handler also appends `name` (`r.FormValue(&amp;#34;name&amp;#34;)`) to the query string without `url.QueryEscape`, so an `&amp;amp;` in the operator-supplied key name corrupts query parsing and a `\r\n` in older proxies could split response headers.&lt;/p&gt;
&lt;p&gt;## Affected
All released versions up to v0.3.1.&lt;/p&gt;
&lt;p&gt;## Reproducer
As admin, create an API key via `/ui/operators/&amp;lt;id&amp;gt;/api-keys` (form POST). The 303 Location header carries the raw token in the query string. Open browser DevTools → Network → response headers; or check the reverse-proxy access log; or check the operator-detail page&amp;#39;s `Referer`-emitting fetches.&lt;/p&gt;
&lt;p&gt;## Suggested fix
Stash the raw key in a one-shot server-side flash storage (e.g., a row in `…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9pg3-25fq-p6cc</guid>
    </item>
  </channel>
</rss>
