Sliver Vulnerable to Authenticated OOM via Memory Exhaustion in mTLS/WireGuard Transports

Summary

Sliver is a command and control framework that uses a custom Wireguard netstack. Versions 1.7.3 and below contain a Remote OOM (Out-of-Memory) vulnerability in the Sliver C2 server's mTLS and WireGuard C2 transport layer. The socketReadEnvelope and socketWGReadEnvelope functions trust an attacker-controlled 4-byte length prefix to allocate memory, with ServerMaxMessageSize allowing single allocations of up to ~2 GiB. A compromised implant or an attacker with valid credentials can exploit this by sending fabricated length prefixes over concurrent yamux streams (up to 128 per connection), forcing the server to attempt allocating ~256 GiB of memory and triggering an OS OOM kill. This crashes the Sliver server, disrupts all active implant sessions, and may degrade or kill other processes sharing the same host. The same pattern also affects all implant-side readers, which have no upper-bound check at all. The issue was not fixed at the the time of publication.

Timeline

1. Mar 20, 2026, 3:37 AM UTCCVE published
2. Mar 21, 2026, 2:53 AM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: no · Technical impact: partial

3. Mar 21, 2026, 2:53 AM UTCRecord last updated

Affected versions

• BishopFox sliver

  through 1.7.3

• github.com/bishopfox/sliverGo

  through 1.7.3

• github.com/bishopfox/sliverGo

  All versions

References 2