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

Advisory record · `GHSA-273q-qgh5-wrj6`

- **Identifiers:** `GHSA-273q-qgh5-wrj6` · `CVE-2026-47725` · `GO-2026-5049`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-269](https://cwe.mitre.org/data/definitions/269.html) · [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Privilege escalation](https://agentprime.io/advisories/tag/privilege-escalation.md) · [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 8 Jun 2026
- **Updated:** 17 Jun 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `github.com/juev/nebula-mesh` (Go): affected `<0.3.3`; fixed in `0.3.3`

## 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

- 6.9 Medium, CVSS 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`, from 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

- 31 Oct 2026, 15:08 UTC: First seen by agentprime
- 31 Oct 2026, 15:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-273q-qgh5-wrj6)

## Sources

- [GitHub Advisory Database: GHSA-273q-qgh5-wrj6](https://github.com/advisories/GHSA-273q-qgh5-wrj6)
- [OSV: GHSA-273q-qgh5-wrj6](https://osv.dev/vulnerability/GHSA-273q-qgh5-wrj6)
- <https://github.com/juev/nebula-mesh/security/advisories/GHSA-273q-qgh5-wrj6>
- <https://github.com/juev/nebula-mesh>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-273q-qgh5-wrj6>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-273q-qgh5-wrj6/>. Everything for agents: <https://agentprime.io/llms.txt>.