CVE-2025-27093 affects the Sliver command-and-control framework’s custom WireGuard netstack in versions 1.5.43 and earlier, as well as the 1.6.0-dev development version. The vulnerable netstack does not enforce traffic restrictions between WireGuard clients, allowing peers on the Sliver WireGuard network to communicate with each other without intended isolation. As a result, compromised or additional WireGuard clients can reach services exposed by other clients, including operator-host services bound to the WireGuard interface, and can access port forwards that were expected to be limited. The issue is effectively a missing authorization/network-segmentation control within the WireGuard client mesh, rather than a memory corruption flaw.
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.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.