{"api_version":"1","generated_at":"2026-09-05T10:54:48+00:00","cve":"CVE-2026-61699","urls":{"html":"https://cve.report/CVE-2026-61699","api":"https://cve.report/api/cve/CVE-2026-61699.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-61699","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-61699"},"summary":{"title":"nebula-mesh: Certificate revocation is never enforced at the mesh","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.","state":"PUBLISHED","assigner":"GitHub_M","published_at":"2026-09-04 20:17:24","updated_at":"2026-09-04 20:17:24"},"problem_types":["CWE-299","CWE-672","CWE-299 CWE-299: Improper Check for Certificate Revocation","CWE-672 CWE-672: Operation on a Resource after Expiration or Release"],"metrics":[{"version":"3.1","source":"security-advisories@github.com","type":"Secondary","score":"8.1","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","baseScore":8.1,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"8.1","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","data":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":8.1,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"}}],"references":[{"url":"https://github.com/forgekeep/nebula-mesh/releases/tag/v0.7.1","name":"https://github.com/forgekeep/nebula-mesh/releases/tag/v0.7.1","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-cm26-5974-52h8","name":"https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-cm26-5974-52h8","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/forgekeep/nebula-mesh/commit/0426e2f224a9b1e2029029bf923c93ed39d21cdb","name":"https://github.com/forgekeep/nebula-mesh/commit/0426e2f224a9b1e2029029bf923c93ed39d21cdb","refsource":"security-advisories@github.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-61699","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-61699","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"forgekeep","product":"nebula-mesh","version":"affected < 0.7.1","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"product":"nebula-mesh","vendor":"forgekeep","versions":[{"status":"affected","version":"< 0.7.1"}]}],"descriptions":[{"lang":"en","value":"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."}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":8.1,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-299","description":"CWE-299: Improper Check for Certificate Revocation","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-672","description":"CWE-672: Operation on a Resource after Expiration or Release","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-09-04T19:43:28.633Z","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M"},"references":[{"name":"https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-cm26-5974-52h8","tags":["x_refsource_CONFIRM"],"url":"https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-cm26-5974-52h8"},{"name":"https://github.com/forgekeep/nebula-mesh/commit/0426e2f224a9b1e2029029bf923c93ed39d21cdb","tags":["x_refsource_MISC"],"url":"https://github.com/forgekeep/nebula-mesh/commit/0426e2f224a9b1e2029029bf923c93ed39d21cdb"},{"name":"https://github.com/forgekeep/nebula-mesh/releases/tag/v0.7.1","tags":["x_refsource_MISC"],"url":"https://github.com/forgekeep/nebula-mesh/releases/tag/v0.7.1"}],"source":{"advisory":"GHSA-cm26-5974-52h8","discovery":"UNKNOWN"},"title":"nebula-mesh: Certificate revocation is never enforced at the mesh"}},"cveMetadata":{"assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","assignerShortName":"GitHub_M","cveId":"CVE-2026-61699","datePublished":"2026-09-04T19:43:28.633Z","dateReserved":"2026-07-10T18:36:58.851Z","dateUpdated":"2026-09-04T19:43:28.633Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-04 20:17:24","lastModifiedDate":"2026-09-04 20:17:24","problem_types":["CWE-299","CWE-672","CWE-299 CWE-299: Improper Check for Certificate Revocation","CWE-672 CWE-672: Operation on a Resource after Expiration or Release"],"metrics":{"cvssMetricV31":[{"source":"security-advisories@github.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","baseScore":8.1,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE"},"exploitabilityScore":2.8,"impactScore":5.2}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"61699","Ordinal":"1","Title":"nebula-mesh: Certificate revocation is never enforced at the mes","CVE":"CVE-2026-61699","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"61699","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"nebula-mesh: Certificate revocation is never enforced at the mes"}]}}}