{"answers":{"affected":"3 open source packages ship an affected version, including github.com/juev/nebula-mesh.","exploited":"There is no known exploitation of CVE-2026-47724 in the wild and no public exploit code.","fix":"Upgrade github.com/juev/nebula-mesh to 0.3.4 or later.","what":"CVE-2026-47724 is a critical missing authorization vulnerability in juev nebula-mesh, published on 23 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47724 and fix it if it is affected.\n\nWhat it is: CVE-2026-47724 is a critical missing authorization vulnerability in juev nebula-mesh, published on 23 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-47724 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/juev/nebula-mesh (Go): affected all versions; fixed in 0.3.4\n- github.com/juev/nebula-mesh (Go): affected all versions; fixed in 0.3.4\n- github.com/juev/nebula-mesh (Go): affected all versions; fixed in 0.3.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-47724/ (Markdown: https://insights.sbomify.com/CVE-2026-47724/index.md)","id":"CVE-2026-47724","markdown":"https://insights.sbomify.com/CVE-2026-47724/index.md","name":"CVE-2026-47724","record":{"aliases":["GHSA-598g-h2vc-h5vg","GO-2026-5139"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Nebula mesh control plane","requires_auth":"low_privilege","summary":"Attackers with operator API keys can bypass ownership checks to access other tenants' resources, leading to privilege escalation and data modification.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.4, the `/api/v1/*` route surface trusts the bearer token alone for authorisation on most endpoints. The codebase itself admits this at `internal/api/hosts.go:384`: \"API trusts the bearer token for authorisation; per-CA ownership is enforced only in the Web layer.\" The Web UI gates state-changing routes through `loadAccessibleCA` (`internal/web/cas.go`); CA-management endpoints in `internal/api/cas.go` ALSO have proper `canAccessCA` gates. The gap is on the host, network, firewall, mobile-bundle, and most operator endpoints. Combined with the per-operator CA model from ADR 0002, this gives any non-admin operator API key broad cross-tenant access — instant privilege escalation in the worst case. Version 0.3.4 fixes the issue.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"nebula-mesh: API endpoints lack ownership checks, enabling cross-operator privilege escalation","id":"CVE-2026-47724","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"nebula-mesh: Web UI lacks CSRF tokens on /ui/* mutating endpoints","id":"CVE-2026-47725"},"packages":[{"ecosystem":"Go","fixed":["0.3.4"],"introduced":["0"],"last_affected":[],"package":"github.com/juev/nebula-mesh","purl":null,"source":"GHSA-598g-h2vc-h5vg"},{"ecosystem":"Go","fixed":["0.3.4"],"introduced":["0"],"last_affected":[],"package":"github.com/juev/nebula-mesh","purl":"pkg:golang/github.com/juev/nebula-mesh","source":"GHSA-598g-h2vc-h5vg"},{"ecosystem":"Go","fixed":["0.3.4"],"introduced":["0"],"last_affected":[],"package":"github.com/juev/nebula-mesh","purl":"pkg:golang/github.com/juev/nebula-mesh","source":"GO-2026-5139"}],"prev":{"headline":"nebula-mesh: Web UI and API responses lack security headers (CSP, X-Frame-Options, HSTS, etc.)","id":"CVE-2026-47723"},"products":["nebula-mesh"],"published":"2026-07-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["juev"]},"summary":"Attackers with operator API keys can bypass ownership checks to access other tenants' resources, leading to privilege escalation and data modification.","url":"https://insights.sbomify.com/CVE-2026-47724/"}