{"answers":{"affected":"3 open source packages ship an affected version, including github.com/forgekeep/nebula-mesh.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61699 exists.","fix":"Upgrade github.com/forgekeep/nebula-mesh to 0.7.1 or later.","what":"CVE-2026-61699 is a high-severity vulnerability in forgekeep nebula-mesh, published on 4 Sep 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-61699 and fix it if it is affected.\n\nWhat it is: CVE-2026-61699 is a high-severity vulnerability in forgekeep nebula-mesh, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61699 exists.\n\nAffected packages and fixed versions:\n- github.com/forgekeep/nebula-mesh (Go): affected all versions; fixed in 0.7.1\n- github.com/forgekeep/nebula-mesh (Go): affected all versions; fixed in 0.7.1\n- github.com/forgekeep/nebula-mesh (Go): affected all versions; fixed in 0.7.1\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-61699/ (Markdown: https://insights.sbomify.com/CVE-2026-61699/index.md)","id":"CVE-2026-61699","markdown":"https://insights.sbomify.com/CVE-2026-61699/index.md","name":"CVE-2026-61699","record":{"aliases":["GHSA-cm26-5974-52h8","GO-2026-5986"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Nebula mesh control plane","requires_auth":"low_privilege","summary":"Attackers with stolen keys bypass certificate revocation in nebula-mesh, maintaining unauthorized network access despite operator blocking.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-672","name":"Operation on a Resource after Expiration or Release"},{"id":"CWE-299","name":"Improper Check for Certificate Revocation"}],"description":"nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. Prior to version 0.7.1, revocation is the only in-band mechanism that isolates a compromised/offboarded host from a Nebula mesh. Because the blocklist never reaches any peer's config.yml, a Blocked host retains full overlay reachability to every peer under its CA (and internal services on the mesh) for up to 30d (agent) / 365d (mobile). An attacker who exfiltrates host.key+host.crt can run stock slackhq/nebula directly, ignore the agent's 403/410 poll responses, and stay connected after the operator revokes the host. Operator-visible state (UI shows blocked, audit log records it) is misleading. This issue has been patched in version 0.7.1.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"nebula-mesh: Certificate revocation is never enforced at the mesh","id":"CVE-2026-61699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"MariaDB Connector/J does not enforce allowLocalInfile=false on server-initiated LOCAL INFILE requests","id":"CVE-2026-61700"},"packages":[{"ecosystem":"Go","fixed":["0.7.1"],"introduced":["0"],"last_affected":[],"package":"github.com/forgekeep/nebula-mesh","purl":null,"source":"GHSA-cm26-5974-52h8"},{"ecosystem":"Go","fixed":["0.7.1"],"introduced":["0"],"last_affected":[],"package":"github.com/forgekeep/nebula-mesh","purl":"pkg:golang/github.com/forgekeep/nebula-mesh","source":"GHSA-cm26-5974-52h8"},{"ecosystem":"Go","fixed":["0.7.1"],"introduced":["0"],"last_affected":[],"package":"github.com/forgekeep/nebula-mesh","purl":"pkg:golang/github.com/forgekeep/nebula-mesh","source":"GO-2026-5986"}],"prev":{"headline":"Forem: Stored XSS in Admin Abuse Report Rendering","id":"CVE-2026-61696"},"products":["nebula-mesh"],"published":"2026-09-04","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-08","vendors":["forgekeep"]},"summary":"Attackers with stolen keys bypass certificate revocation in nebula-mesh, maintaining unauthorized network access despite operator blocking.","url":"https://insights.sbomify.com/CVE-2026-61699/"}