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

CVE-2026-32941 · Severity: medium · CVSS 4 · Published 2026-03-26

Sliver Vulnerable to Authenticated OOM via Memory Exhaustion in mTLS/WireGuard Transports in github.com/bishopfox/sliver

Technologies: github.com/bishopfox/sliver (Go). Vendors: Go.

Quick answers

Is CVE-2026-32941 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-32941 being exploited in the wild.
How severe is CVE-2026-32941?
Medium severity, with a CVSS score of 4, published 26 March 2026.
Which products and versions are affected?
github.com/bishopfox/sliver (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.7.3.
Is there a fix for CVE-2026-32941?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-32941?
Check whether you run github.com/bishopfox/sliver (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • github.com/bishopfox/sliver (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.7.3

Identifiers

  • CVE-2026-32941
  • GHSA-97vp-pwqj-46qc
  • GO-2026-4723

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.