Privilege Escalation in github.com/juev/nebula-mesh (CVE-2026-47725)
Summary
Vulnerability in github.com/juev/nebula-mesh (CVE-2026-47725). Risk of unauthorized operations or information disclosure. Exploitable via GET /ui/logout. Mitigation: upgrade to 0.3.3 or later.
Original description
The description as published by the source.
nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.3, 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 can force-trigger. This issue has been patched in version 0.3.3.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47725 has been found in github.com/juev/nebula-mesh.
Attackers can target a specific entry point like GET /ui/logout over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/juev/nebula-mesh to 0.3.3 or later.
If unsure, ask your IT team or search "github.com/juev/nebula-mesh CVE-2026-47725" on the vendor's site.
CVE-2026-47725 (github.com/juev/nebula-mesh) — CWE-269
Attack surface: GET /ui/logout / _csrf / Login / StartAuthenticatedSession
Patched: 0.3.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-269) exists in github.com/juev/nebula-mesh. Attackers reach the vulnerable code path via GET /ui/logout.
Check the vendor advisory for the affected versions of github.com/juev/nebula-mesh. Attack surface: GET /ui/logout / _csrf / Login / StartAuthenticatedSession.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.3.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /ui/logout requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/juev/nebula-mesh' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/juev/nebula-mesh' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/juev/nebula-meshを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /ui/logout' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /ui/logoutへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/juev/nebula-mesh to 0.3.3ステージング環境で 0.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /ui/logout on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com