CVE-2026-61699 is a certificate validation flaw in nebula-mesh in which certificate revocation is not enforced across the mesh. Agent-side handling of the per-CA blocklist is not implemented, and generated agent configuration omits the pki.blocklist setting. As a result, certificates associated with blocked, offboarded, or compromised hosts remain trusted by peer nodes until the certificates naturally expire rather than being rejected after revocation. The issue affects the mesh trust model by preventing timely invalidation of previously issued credentials.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.