CVE-2026-47725: juev nebula-mesh · Cross-Site Request Forgery (CSRF)
Affects juev nebula-meshSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 0.3.3 when convenient.
Data as of 27 Oct 2026, 05:11 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.3.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade juev nebula-mesh to 0.3.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| juevnebula-mesh | Affected
| Fixed in
|
AI-suggested
Upgrade to juev nebula-mesh version 0.3.3 or later, where this CSRF vulnerability has been patched. No other official remediation or temporary fixes are indicated. Until upgrading, be aware of the risk from cross-site requests and consider additional protective measures such as implementing CSRF tokens or restricting access to sensitive endpoints.
Description
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 <img src=".../ui/logout"> can force-trigger. This issue has been patched in version 0.3.3.