CVE-2026-32941

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

March 20, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Aug 4, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Authenticated OOM via Memory Exhaustion in mTLS/WireGuard Transports · Advisory · BishopFox/sliver · GitHub

https://github.com/BishopFox/sliver/security/advisories/GHSA-97vp-pwqj-46qc

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
gogithub.com/bishopfox/sliver—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/bishopfox/sliver———

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 187 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 17:08 UTCOSV refresh
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-24 14:17 UTCEPSS rescore
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 11:04 UTCEG score recompute
  11. 2026-08-16 11:04 UTCGHSA enrichment
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 07:15 UTCEG score recompute
  15. 2026-08-14 07:15 UTCGHSA enrichment
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-12 21:56 UTCEG score recompute
  18. 2026-08-12 21:56 UTCGHSA enrichment
  19. 2026-08-12 13:50 UTCEPSS rescore
  20. 2026-08-11 07:36 UTCEG score recompute
  21. 2026-08-11 07:36 UTCGHSA enrichment
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 07:12 UTCEG score recompute
  24. 2026-08-10 07:12 UTCGHSA enrichment
  25. 2026-08-09 13:46 UTCEPSS rescore
  26. 2026-08-09 06:48 UTCEG score recompute
  27. 2026-08-09 06:48 UTCGHSA enrichment
  28. 2026-08-08 16:37 UTCEPSS rescore
  29. 2026-08-07 17:18 UTCEG score recompute
  30. 2026-08-07 17:18 UTCGHSA enrichment
  31. 2026-08-06 13:46 UTCEPSS rescore
  32. 2026-08-06 01:29 UTCEG score recompute
  33. 2026-08-06 01:29 UTCGHSA enrichment
  34. 2026-08-05 19:17 UTCEPSS rescore
  35. 2026-08-04 15:10 UTCEPSS rescore
  36. 2026-08-04 10:38 UTCEPSS rescore
  37. 2026-08-04 00:37 UTCEG score recompute
  38. 2026-08-04 00:37 UTCGHSA enrichment
  39. 2026-08-03 10:36 UTCEPSS rescore
  40. 2026-08-02 16:15 UTCEG score recompute
  41. 2026-08-02 16:15 UTCGHSA enrichment
  42. 2026-08-02 02:27 UTCEPSS rescore
  43. 2026-08-01 04:16 UTCEPSS rescore
  44. 2026-07-30 16:28 UTCEPSS rescore
  45. 2026-07-30 01:30 UTCEPSS rescore
  46. 2026-07-27 14:13 UTCEPSS rescore
  47. 2026-07-26 14:54 UTCEPSS rescore
  48. 2026-07-26 14:54 UTCEPSS rescore
  49. 2026-07-25 14:18 UTCEPSS rescore
  50. 2026-07-25 14:18 UTCEPSS rescore
  51. 2026-07-24 14:17 UTCEPSS rescore
  52. 2026-07-24 14:17 UTCEPSS rescore
  53. 2026-07-23 14:18 UTCEPSS rescore
  54. 2026-07-23 14:18 UTCEPSS rescore
  55. 2026-07-23 03:09 UTCEG score recompute
  56. 2026-07-22 14:08 UTCEPSS rescore
  57. 2026-07-21 15:24 UTCEPSS rescore
  58. 2026-07-20 17:08 UTCEPSS rescore
  59. 2026-07-20 17:08 UTCEPSS rescore
  60. 2026-07-19 14:31 UTCEPSS rescore
  61. 2026-07-19 14:31 UTCEPSS rescore
  62. 2026-07-19 02:29 UTCEPSS rescore
  63. 2026-07-18 10:04 UTCEPSS rescore
  64. 2026-07-18 10:04 UTCEPSS rescore
  65. 2026-07-17 07:46 UTCOSV refresh
  66. 2026-07-16 17:03 UTCEPSS rescore
  67. 2026-07-16 17:03 UTCEPSS rescore
  68. 2026-07-15 16:57 UTCEPSS rescore
  69. 2026-07-15 16:57 UTCEPSS rescore
  70. 2026-07-15 02:00 UTCEPSS rescore
  71. 2026-07-15 02:00 UTCEPSS rescore
  72. 2026-07-13 22:30 UTCEPSS rescore
  73. 2026-07-13 06:13 UTCEPSS rescore
  74. 2026-07-13 06:13 UTCEPSS rescore
  75. 2026-07-12 05:46 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCskoveit/CVE-2026-32941
    First seen Mar 3, 2026

    CVE-2026-32941 PoC - Sliver Remote OOM

    Open source ↗

Frequently asked(5)

What is CVE-2026-32941?
CVE-2026-32941 is a medium vulnerability published on March 20, 2026. 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…
When was CVE-2026-32941 disclosed?
CVE-2026-32941 was first published in the National Vulnerability Database on March 20, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32941 actively exploited?
CVE-2026-32941 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.3% of all scored CVEs.
What is the CVSS score of CVE-2026-32941?
CVE-2026-32941 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-32941?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32941, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32941

Explore →

Is Your Infrastructure Affected by CVE-2026-32941?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs