Advisory record · GHSA-273q-qgh5-wrj6

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

CVSS 6.9 MediumEPSS 0.0019 · 8th percentile

Published by the GitHub Advisory Database at 8 Jun 2026, 23:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/juev/nebula-meshGo<0.3.30.3.3
Identifiers
GHSA-273q-qgh5-wrj6 · CVE-2026-47725 · GO-2026-5049
Weakness (CWE)
CWE-269 · CWE-352
Published
8 Jun 2026
Updated
17 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of github.com/juev/nebula-mesh before 0.3.3 have a cross-site request forgery weakness: the web UI's /ui/* POST, PUT, PATCH and DELETE routes act on any request carrying a valid session cookie, without a CSRF token check. An attacker who gets an authenticated operator to visit a crafted page can make the UI sign or delete CA certificates, mint API keys, disable operators and change settings, and can also force a logout through the GET /ui/logout route. Upgrade to version 0.3.3, which adds CSRF protection.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.9 Medium 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0019, the 8th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:08 UTC First seen by agentprime
  2. 31 Oct 2026, 15:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.