<?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 06:30:44 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-340498</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-340498</link>
      <description>EUVD-2026-340498</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-340498</guid>
    </item>
    <item>
      <title>fkie_cve-2026-47722</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-47722</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, `internal/configgen/generator.go:86,108,119` interpolates the operator-supplied `ListenHost` and `TunDevice` fields raw into a `text/template` that produces the agent&amp;#39;s `config.yml`. `internal/web/advanced.go:20-35` accepts both with only `strings.TrimSpace` — no character or shape validation. Version 0.3.2 fixes the issue.&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, `internal/configgen/generator.go:86,108,119` interpolates the operator-supplied `ListenHost` and `TunDevice` fields raw into a `text/template` that produces the agent&amp;#39;s `config.yml`. `internal/web/advanced.go:20-35` accepts both with only `strings.TrimSpace` — no character or shape validation. Version 0.3.2 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-47722</guid>
    </item>
    <item>
      <title>GHSA-7hp6-g3pq-3pc3 — nebula-mesh: Host advanced overrides allow YAML injection into agent config.yml</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7hp6-g3pq-3pc3</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/configgen/generator.go:86,108,119` interpolates the operator-supplied `ListenHost` and `TunDevice` fields raw into a `text/template` that produces the agent&amp;#39;s `config.yml`. `internal/web/advanced.go:20-35` accepts both with only `strings.TrimSpace` — no character or shape validation.&lt;/p&gt;
&lt;p&gt;## Exploit
An operator (or attacker with any operator key, given the cross-tenant CRUD advisory) sets `adv_tun_device` to:&lt;/p&gt;
&lt;p&gt;```
nebula0
lighthouse:
  am_lighthouse: true
  hosts: [&amp;#34;10.0.0.1&amp;#34;]
#
```&lt;/p&gt;
&lt;p&gt;The agent fetches the rendered config on its next signed poll. On config reload, it loads the injected YAML keys: the host self-promotes to lighthouse, attracts mesh traffic, or sets `am_relay: true` to be selected as a relay. The `ListenHost` field has the same shape.&lt;/p&gt;
&lt;p&gt;## Affected
All released versions prior to v0.3.2.&lt;/p&gt;
&lt;p&gt;## Threat model
- **Today**: operator can compromise their own host&amp;#39;s config (trivially allowed if they own the host, but they can also set lighthouse/relay flags that the operator-create form does NOT expose — privilege uplift within their own tenant).
- **Combined with the critical /api/v1 authz advisory**: any operator key can mutate ANOTHER tenant&amp;#39;s host overrides and inject YAML there.
- **Post-fix of the authz advisory**: still relevant — the agent unconditionally trusts whatever config the server hands it, so any future operator-impersonation bug re-amplifies this.&lt;/p&gt;
&lt;p&gt;## Suggested fix
Two options, either acceptable:&lt;/p&gt;
&lt;p&gt;1. **Input validation** in `parseAdvancedFromForm`…&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/configgen/generator.go:86,108,119` interpolates the operator-supplied `ListenHost` and `TunDevice` fields raw into a `text/template` that produces the agent&amp;#39;s `config.yml`. `internal/web/advanced.go:20-35` accepts both with only `strings.TrimSpace` — no character or shape validation.&lt;/p&gt;
&lt;p&gt;## Exploit
An operator (or attacker with any operator key, given the cross-tenant CRUD advisory) sets `adv_tun_device` to:&lt;/p&gt;
&lt;p&gt;```
nebula0
lighthouse:
  am_lighthouse: true
  hosts: [&amp;#34;10.0.0.1&amp;#34;]
#
```&lt;/p&gt;
&lt;p&gt;The agent fetches the rendered config on its next signed poll. On config reload, it loads the injected YAML keys: the host self-promotes to lighthouse, attracts mesh traffic, or sets `am_relay: true` to be selected as a relay. The `ListenHost` field has the same shape.&lt;/p&gt;
&lt;p&gt;## Affected
All released versions prior to v0.3.2.&lt;/p&gt;
&lt;p&gt;## Threat model
- **Today**: operator can compromise their own host&amp;#39;s config (trivially allowed if they own the host, but they can also set lighthouse/relay flags that the operator-create form does NOT expose — privilege uplift within their own tenant).
- **Combined with the critical /api/v1 authz advisory**: any operator key can mutate ANOTHER tenant&amp;#39;s host overrides and inject YAML there.
- **Post-fix of the authz advisory**: still relevant — the agent unconditionally trusts whatever config the server hands it, so any future operator-impersonation bug re-amplifies this.&lt;/p&gt;
&lt;p&gt;## Suggested fix
Two options, either acceptable:&lt;/p&gt;
&lt;p&gt;1. **Input validation** in `parseAdvancedFromForm`…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7hp6-g3pq-3pc3</guid>
    </item>
  </channel>
</rss>
