CVE-2026-47723: nebula-mesh: Web UI and API responses lack security headers (CSP, X-Frame-Options, HSTS, etc.)
None of the response paths in internal/web/ or internal/api/ set the standard browser-security headers. grep for Content-Security-Policy, X-Frame-Options, Strict-Transport-Security, X-Content-Type-Options, Referrer-Policy returns zero matches across the codebase. Impact The admin UI signs CA certificates, mints API keys (returned inline once per page), displays TOTP QR codes, and exposes operator-management forms.
Published Jun 8, 2026
Affected packages
github.com/juev/nebula-mesh
- Ecosystem
- Go
- Affected
- <= 0.3.0
- Fixed in
- 0.3.1
- Check
go list -m github.com/juev/nebula-mesh
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
None of the response paths in internal/web/ or internal/api/ set the standard browser-security headers. grep for Content-Security-Policy, X-Frame-Options, Strict-Transport-Security, X-Content-Type-Options, Referrer-Policy returns zero matches across the codebase.
Impact
The admin UI signs CA certificates, mints API keys (returned inline once per page), displays TOTP QR codes, and exposes operator-management forms. Missing X-Frame-Options: DENY / frame-ancestors 'none' is a real clickjacking lever against an admin browsing /ui/operators/* or /ui/cas/*. Missing X-Content-Type-Options: nosniff allows MIME confusion on any user-supplied content surface. Missing HSTS on TLS deployments leaves a downgrade window.
Affected
All released versions up to v0.3.0.
Suggested fix
A single response-header middleware mounted at the chi router root in both /ui/* and /api/* paths:
func securityHeadersMiddleware(next http.Handler) http.Handler {
return http.HandlerFunc(func(rw http.ResponseWriter, r *http.Request) {
h := rw.Header()
h.Set("Content-Security-Policy",
"default-src 'self'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'")
h.Set("X-Content-Type-Options", "nosniff")
h.Set("Referrer-Policy", "same-origin")
h.Set("X-Frame-Options", "DENY") // belt-and-braces; CSP frame-ancestors is the modern path
if r.TLS != nil {
h.Set("Strict-Transport-Security", "max-age=31536000; includeSubDomains")
}
next.ServeHTTP(rw, r)
})
}The inline <script> in layout.html for CSRF wiring (added in the CSRF advisory) will need either a nonce, a hash in CSP, or external-file extraction. Easiest path: a nonce per request (crypto/rand, base64) injected into both the CSP header and the script's nonce="" attribute.
Credited to ak2k.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-49258
Nebula Mesh: Web UI lacks ownership checks, enabling cross-operator access to hosts and networks (read, block, delete)
high8.8No fixJun 26, 2026GHSA-v2jf-442r-6mjh
nebula-mesh: Signed-poll nonce LRU is in-memory and bounded; replay survives restart + eviction
low2.7Jun 26, 2026GHSA-ghmh-jhmj-wcmf
nebula-mesh's stores enrollment tokens unhashed in SQLite
medium5.0Jun 22, 2026GHSA-6vgg-xhvh-38ff
nebula-mesh: POST /api/v1/hosts/{id}/mobile-bundle response lacks Cache-Control: no-store
low2.3Jun 12, 2026CVE-2026-47768
nebula-mesh: Newly-minted operator API key exposed in redirect URL (Referer, history, proxy logs)
medium5.5Jun 10, 2026CVE-2026-48025
nebula-mesh: Decrypted CA private key persists in heap after signing
mediumJun 10, 2026
