{"id":"EUVD-2026-71715","enisaUuid":"40cdaebc-c16e-3eb0-9f27-ceea719d6962","description":"nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. Prior to version 0.3.7, two related authorization gaps let a host that should no longer be trusted obtain a fresh, valid Nebula certificate, because nebula-mgmt does not re-evaluate revocation/authorization state at certificate issuance time — only at poll time. Firstly, the blocklist is not enforced at sign / re-enroll time. internal/api/enroll.go:128 calls caMgr.Sign(...) without consulting the blocklist. The blocklist is only checked in the poll path (internal/api/updates.go:57, fingerprintInBlocklist). The blocklist is keyed by certificate fingerprint (internal/store/sqlite.go), so a re-enrollment produces a new fingerprint that is not in the blocklist. Secondly, renewal does not re-validate operator / CA status. Auto-renewal at poll time (internal/api/updates.go:285-319, signHostCert) reads host.Name, host.Groups, host.NebulaIPs from the DB and re-signs without checking whether the owning operator is still active or the CA still valid. DisableOperator (internal/store/sqlite_operators.go) revokes sessions and API keys but does not retire the operator\u0027s CAs, and pki/signer.go checks only CA cert time-expiry, not operator/CA status. This issue has been patched in version 0.3.7.","datePublished":"Sep 4, 2026, 7:40:16 PM","dateUpdated":"Sep 4, 2026, 7:50:03 PM","baseScore":6.9,"baseScoreVersion":"4.0","baseScoreVector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","references":"https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-339v-266x-79xr\nhttps://github.com/forgekeep/nebula-mesh/issues/178\nhttps://github.com/forgekeep/nebula-mesh/releases/tag/v0.3.7\n","aliases":"CVE-2026-53602\nGHSA-339v-266x-79xr\n","assigner":"GitHub_M","epss":0.31,"enisaIdProduct":[{"id":"53f838d0-c2e9-3fcb-84f0-5c2084950bb3","product":{"name":"nebula-mesh","vendor":{"name":"juev"}},"product_version":"\u003c 0.3.7"}],"enisaIdVendor":[{"id":"9db79e3c-42e6-3c1d-a9da-e50a63f9eb85","vendor":{"name":"forgekeep"}}],"enisaIdVulnerability":[{"id":"4edb28e3-cd22-3a74-af66-934aa40130d7","vulnerability":{"id":"CVE-2026-53602","description":"nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. Prior to version 0.3.7, two related authorization gaps let a host that should no longer be trusted obtain a fresh, valid Nebula certificate, because nebula-mgmt does not re-evaluate revocation/authorization state at certificate issuance time — only at poll time. Firstly, the blocklist is not enforced at sign / re-enroll time. internal/api/enroll.go:128 calls caMgr.Sign(...) without consulting the blocklist. The blocklist is only checked in the poll path (internal/api/updates.go:57, fingerprintInBlocklist). The blocklist is keyed by certificate fingerprint (internal/store/sqlite.go), so a re-enrollment produces a new fingerprint that is not in the blocklist. Secondly, renewal does not re-validate operator / CA status. Auto-renewal at poll time (internal/api/updates.go:285-319, signHostCert) reads host.Name, host.Groups, host.NebulaIPs from the DB and re-signs without checking whether the owning operator is still active or the CA still valid. DisableOperator (internal/store/sqlite_operators.go) revokes sessions and API keys but does not retire the operator\u0027s CAs, and pki/signer.go checks only CA cert time-expiry, not operator/CA status. This issue has been patched in version 0.3.7.","datePublished":"Sep 4, 2026, 7:40:16 PM","dateUpdated":"Sep 4, 2026, 7:50:03 PM","status":"PUBLISHED","baseScore":6.9,"baseScoreVersion":"4.0","baseScoreVector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","references":"https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-339v-266x-79xr\nhttps://github.com/forgekeep/nebula-mesh/issues/178\nhttps://github.com/forgekeep/nebula-mesh/releases/tag/v0.3.7\n","enisa_id":"EUVD-2026-71715\n","assigner":"GitHub_M","epss":0.31,"dataProcessed":"Nov 15, 2026, 7:20:41 AM","vulnerabilityProduct":[{"id":"3fb0c077-7418-3a95-b06f-2170b9c517fd","product":{"name":"nebula-mesh","vendor":{"name":"juev"}},"product_version":"\u003c 0.3.7"}],"vulnerabilityVendor":[{"id":"471d1454-d438-349f-8567-1a44b3c7205c","vendor":{"name":"forgekeep"}}]}},{"id":"fbadd798-9d8b-3df9-816a-a770c18fd277","vulnerability":{"id":"GHSA-339v-266x-79xr","description":"nebula-mesh: Host revocation is not durable - blocked/offboarded hosts can regain a valid certificate","datePublished":"Jul 9, 2026, 8:52:27 PM","dateUpdated":"Jul 9, 2026, 8:52:27 PM","baseScore":0.0,"references":"https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-339v-266x-79xr\nhttps://github.com/forgekeep/nebula-mesh/issues/178\nhttps://github.com/forgekeep/nebula-mesh\n","enisa_id":"EUVD-2026-71715\n","aliases":"CVE-2026-53602\nGHSA-339v-266x-79xr\n","epss":0.0,"dataProcessed":"Nov 15, 2026, 2:52:09 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}}],"enisaIdAdvisory":[]}