GHSA-hjr9-wj7v-7hv8: Sliver Vulnerable to Pre-Auth Memory Exhaustion via NoEncoder Bypass
Summary A specially crafted nonce routes unauthenticated requests through the NoEncoder path, where startSessionHandler() reads the entire request body without limits, allowing attacker-driven memory exhaustion and process crash. Details - server/encoders/encoders.go: EncoderFromNonce() returns NoEncoder when nonce % 65537 == 0 (lines 254-264); NoEncoder is a passthrough (util/encoders/nop.go:22-32).
Published Jan 5, 2026
Affected packages
github.com/bishopfox/sliver
- Ecosystem
- Go
- Affected
- >= 1.5.0, <= 1.5.44
- Fixed in
- No patched version yet
- Check
go list -m github.com/bishopfox/sliver
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A specially crafted nonce routes unauthenticated requests through the NoEncoder path, where startSessionHandler() reads the entire request body without limits, allowing attacker-driven memory exhaustion and process crash.
Details
server/encoders/encoders.go:EncoderFromNonce()returns NoEncoder whennonce % 65537 == 0(lines 254-264); NoEncoder is a passthrough (util/encoders/nop.go:22-32).server/c2/http.go:anonymousHandler()routes requests with any encoder (including NoEncoder) tostartSessionHandler()(lines 551-562).server/c2/http.go:startSessionHandler()usesio.ReadAll(req.Body)without a size cap (lines 564-643), unlike the authenticated path that usesio.LimitedReader(readReqBody(), lines 708-732).
PoC
An attacker could send an HTTP POST with a nonce that is a multiple of 65537 (e.g., ?q=65537) so it is handled by startSessionHandler() with a NoEncoder, and advertise a very large Content-Length while streaming data. Because this handler uses io.ReadAll(req.Body) without a size limit, the server is expected to allocate large amounts of memory and may exhaust available RAM, leading to process termination on typical deployments.
Impact
Unauthenticated remote DoS: attacker can crash the Sliver HTTP listener, dropping all active sessions and locking out operators until restart. No credentials or non-default config required.
Credited to 0xkato.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-34227
Sliver One-Click Remote Access: Insecure CORS & Unauthenticated MCP Interface
medium5.9Mar 31, 2026GHSA-c279-989m-238f
Sliver: Nil Pointer Dereference in tunnelCloseHandler causes panic when a reverse tunnel (rportfwd) close is attempted
high7.1No fixMar 29, 2026CVE-2026-32941
Sliver Vulnerable to Authenticated OOM via Memory Exhaustion in mTLS/WireGuard Transports
medium5.7No fixMar 17, 2026CVE-2026-29781
Sliver is Vulnerable to Authenticated Nil-Pointer Dereference through its Handlers
low2.1No fixMar 5, 2026CVE-2026-25791
Sliver has DNS C2 OTP Bypass that Allows Unauthenticated Session Flooding and Denial of Service
high7.5Feb 6, 2026CVE-2026-25760
Sliver Vulnerable to Website Path Traversal / Arbitrary File Read (Authenticated)
medium6.5Feb 5, 2026
