# CVE-2026-47725: nebula-mesh: Web UI lacks CSRF tokens on /ui/* mutating endpoints > Attackers can force authenticated users to perform unwanted actions on the nebula-mesh web interface due to missing CSRF tokens on mutating endpoints. - **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 Jul 2026 - **Updated:** 28 Jul 2026 - **Also known as:** GHSA-273q-qgh5-wrj6, GO-2026-5049 ## What is CVE-2026-47725? CVE-2026-47725 is a medium-severity vulnerability in juev nebula-mesh, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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 can force-trigger. This issue has been patched in version 0.3.3. Weakness: CWE-352 (Cross-Site Request Forgery) ## Which versions are affected by CVE-2026-47725? 3 open source packages ship an affected version, including github.com/juev/nebula-mesh. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/juev/nebula-mesh` | Go | All versions | 0.3.3 | | `github.com/juev/nebula-mesh` | Go | All versions | 0.3.3 | | `github.com/juev/nebula-mesh` | Go | All versions | 0.3.3 | ## How do I fix CVE-2026-47725? Upgrade github.com/juev/nebula-mesh to 0.3.3 or later. ## Is CVE-2026-47725 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47725 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-47725 and fix it if it is affected. What it is: CVE-2026-47725 is a medium-severity vulnerability in juev nebula-mesh, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47725 exists. Affected packages and fixed versions: - github.com/juev/nebula-mesh (Go): affected all versions; fixed in 0.3.3 - github.com/juev/nebula-mesh (Go): affected all versions; fixed in 0.3.3 - github.com/juev/nebula-mesh (Go): affected all versions; fixed in 0.3.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-47725/ (Markdown: https://insights.sbomify.com/CVE-2026-47725/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47725 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47725 - OSV: https://osv.dev/vulnerability/CVE-2026-47725 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-47725/ Summaries are generated and may contain mistakes; the official description above is the record.