nebula-mesh's web UI lacks CSRF tokens on /ui/* mutating endpoints

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-47725: 0.19% estimated exploitation activity in the next 30 days; percentile 8.42 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 The admin UI signs CA certificates, mints API keys, rotates / retires / deletes CAs, disables operators, and changes server settings. CSRF here is a real privilege escalation, not just annoyance. Affected All released versions up to v0.3.2. Suggested fix Double-submit cookie: a 32-byte crypto/rand token in a non-HttpOnly csrf cookie, echoed in either X-CSRF-Token (htmx) or a csrf form field (HTML forms). Compared in constant time. Rotated on every privilege transition (Login, OIDC…

Published by the source

8 Jun 2026, 23:09 UTC

Last modified by the source

8 Jun 2026, 23:09 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-273q-qgh5-wrj6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47725

Advisory: nebula-mesh's web UI lacks CSRF tokens on /ui/* mutating endpoints
IDs: CVE-2026-47725, GHSA-273q-qgh5-wrj6
Record: https://patchnext.com/advisories/cve-2026-47725 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/juev/nebula-mesh 0.3.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/juev/nebula-mesh: affected <= 0.3.2; fixed in 0.3.3

## Suggested inspection (read-only)
- Go github.com/juev/nebula-mesh: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/juev/nebula-mesh.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-273q-qgh5-wrj6 (GitHub-reviewed advisory GHSA-273q-qgh5-wrj6 lists affected ranges: Go github.com/juev/nebula-mesh >=0 <=0.3.2)

Commands are suggestions: review each one before running it.