# CVE-2026-32941: Sliver Vulnerable to Authenticated OOM via Memory Exhaustion in mTLS/WireGuard Transports

> An authenticated attacker can crash the Sliver C2 server by sending crafted messages that trigger excessive memory allocation, disrupting all active sessions.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2026
- **Updated:** 21 Mar 2026
- **Also known as:** GHSA-97vp-pwqj-46qc, GO-2026-4723

## What is CVE-2026-32941?

CVE-2026-32941 is a medium-severity denial of service vulnerability in BishopFox sliver, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value), CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-32941?

3 open source packages ship an affected version, including github.com/bishopfox/sliver. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/bishopfox/sliver` | Go | All versions | None |
| `github.com/bishopfox/sliver` | Go | All versions to 1.7.3 | None |
| `github.com/bishopfox/sliver` | Go | All versions to 1.7.3 | None |

Products: Bishopfox Sliver.

## How do I fix CVE-2026-32941?

No fix published yet.

## Is CVE-2026-32941 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32941 exists.

Public exploit code:

- CVE-2026-32941 PoC (github_poc): https://github.com/skoveit/CVE-2026-32941

## Other vulnerabilities in BishopFox sliver

- [CVE-2023-34758](https://insights.sbomify.com/CVE-2023-34758/): Silver vulnerable to MitM attack against implants due to a cryptography vulnerability (high 8.1)
- [CVE-2026-25791](https://insights.sbomify.com/CVE-2026-25791/): Sliver has a DNS C2 OTP Bypass Allows Unauthenticated Session Flooding and Denial of Service (high 7.5)
- [CVE-2025-27090](https://insights.sbomify.com/CVE-2025-27090/): Server-Side Request Forgery (SSRF) in sliver teamserver (medium 6.9)
- [CVE-2026-25760](https://insights.sbomify.com/CVE-2026-25760/): Website Path Traversal / Arbitrary File Read (Authenticated) in Sliver (medium 6.5)
- [CVE-2026-34227](https://insights.sbomify.com/CVE-2026-34227/): Sliver One-Click Remote Access: Insecure CORS & Unauthenticated MCP Interface (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32941 and fix it if it is affected.

What it is: CVE-2026-32941 is a medium-severity denial of service vulnerability in BishopFox sliver, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32941 exists.

Affected packages and fixed versions:
- github.com/bishopfox/sliver (Go): affected all versions; no fix listed
- github.com/bishopfox/sliver (Go): affected all versions up to 1.7.3; no fix listed
- github.com/bishopfox/sliver (Go): affected all versions up to 1.7.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32941/ (Markdown: https://insights.sbomify.com/CVE-2026-32941/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32941
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32941
- OSV: https://osv.dev/vulnerability/CVE-2026-32941

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32941/
Summaries are generated and may contain mistakes; the official description above is the record.