CVE-2026-48058 is a medium-severity security vulnerability in github.com/juev/nebula-mesh (go), affecting versions < 0.3.2. It is fixed in 0.3.2.
internal/web/session.go and internal/web/oidc.go set HttpOnly and SameSite=Lax on every cookie but never Secure. A single plaintext request to the origin (operator on a LAN, mistyped URL, HTTP→HTTPS not strictly enforced, reverse proxy misconfiguration) discloses the session. Affected All released versions up to v0.3.1. Impact An attacker who can observe one HTTP request to the origin recovers the session cookie and impersonates the operator for the remainder of its 24h TTL. The OIDC state cookie has a narrower 10-minute window but enables CSRF on the OIDC callback during that window. Cookie sites internal/web/session.go, Login, StartAuthenticatedSession, CompleteTwoFactor, Logout internal/web/oidc.go, HandleLogin (state set), HandleCallback (state clear) Suggested fix Driven by an explicit cookiesecure config option, inferred true when tlscert+tlskey are configured and false otherwise. ratelimit.trustproxyheader is deliberately not used as a signal, that flag controls XFF parsing for rate-limit IPs and does not promise the proxy speaks TLS to clients. Operator behind a TLS-terminating proxy sets cookiesecure: true explicitly. Logout and OIDC state-clear cookies also pick up matching HttpOnly + SameSite=Lax so browsers reliably replace the original. Reproducer Start nebula-mgmt without tlscert/tlskey (the documented "behind a reverse proxy" deployment). Hit any login flow over the local listener: The Set-Cookie: nebulasession=… line will lack Secure. A subsequent unencrypted hop reveals the cookie verbatim. Operational migration Operators flipping cookie_secure on a running deployment should expect a one-time logout: existing browser cookies have the old attribute set and the new delete-cookie won't match.
go
github.com/juev/nebula-mesh (< 0.3.2)github.com/juev/nebula-mesh → 0.3.2 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-48058 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-48058 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-48058 in your environment →Upgrade github.com/juev/nebula-mesh to 0.3.2 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-48058 is a medium-severity security vulnerability in github.com/juev/nebula-mesh (go), affecting versions < 0.3.2. It is fixed in 0.3.2.
github.com/juev/nebula-mesh (go) versions < 0.3.2 is affected.
Yes. CVE-2026-48058 is fixed in 0.3.2. Upgrade to this version or later.
Whether CVE-2026-48058 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade github.com/juev/nebula-mesh to 0.3.2 or later.