Is github.com/bishopfox/sliver 1.6 vulnerable?
Go · 12 releases from 1.6.0 to 1.6.11 · latest github.com/bishopfox/sliver is 1.7.9 · checked 18 Nov 2026
Yes: 15 known advisories
Yes. github.com/bishopfox/sliver 1.6.11, the last 1.6 release, is affected by 15 known security advisories (3 high, 2 medium, 10 low), including CVE-2026-25791, CVE-2026-34227, CVE-2026-32941. 2 more affect earlier 1.6.x releases. At least one has no fixed release yet.
Is your project on an affected github.com/bishopfox/sliver?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/bishopfox/sliver 1.6.11
Sliver: Unauthenticated Memory Exhaustion Denial of Service in Sliver HTTP(S) Listener PNG Decoder in github.com/bishopfox/sliver
- Affected
- <1.7.6
- Fixed in
- 1.7.6
Sliver One-Click Remote Access: Insecure CORS & Unauthenticated MCP Interface in github.com/bishopfox/sliver
- Affected
- <1.7.4
- Fixed in
- 1.7.4
Sliver: Nil Pointer Dereference in tunnelCloseHandler causes panic when a reverse tunnel (rportfwd) close is attempted in github.com/bishopfox/sliver
- Affected
- All versions
- Fixed in
- No fix released
Sliver One-Click Remote Access: Insecure CORS & Unauthenticated MCP Interface
- Affected
- <1.7.4
- Fixed in
- 1.7.4
Sliver: Nil Pointer Dereference in tunnelCloseHandler causes panic when a reverse tunnel (rportfwd) close is attempted
- Affected
- <=1.7.3
- Fixed in
- No fix released
Sliver Vulnerable to Authenticated OOM via Memory Exhaustion in mTLS/WireGuard Transports in github.com/bishopfox/sliver
- Affected
- All versions
- Fixed in
- No fix released
Sliver Vulnerable to Authenticated OOM via Memory Exhaustion in mTLS/WireGuard Transports
- Affected
- <=1.7.3
- Fixed in
- No fix released
Sliver is Vulnerable to Authenticated Nil-Pointer Dereference through its Handlers in github.com/bishopfox/sliver
- Affected
- All versions
- Fixed in
- No fix released
Sliver is Vulnerable to Authenticated Nil-Pointer Dereference through its Handlers
- Affected
- <=1.7.3
- Fixed in
- No fix released
Sliver has Potential Zip Bomb Denial of Service in GzipEncoder in github.com/bishopfox/sliver
- Affected
- <1.7.2
- Fixed in
- 1.7.2
Sliver has Potential Zip Bomb Denial of Service in GzipEncoder
- Affected
- <1.7.2
- Fixed in
- 1.7.2
Sliver has DNS C2 OTP Bypass that Allows Unauthenticated Session Flooding and Denial of Service in github.com/bishopfox/sliver
- Affected
- All versions
- Fixed in
- No fix released
Sliver has DNS C2 OTP Bypass that Allows Unauthenticated Session Flooding and Denial of Service
- Affected
- <1.6.12
- Fixed in
- 1.6.12
Sliver Vulnerable to Pre-Auth Memory Exhaustion via NoEncoder Bypass in github.com/bishopfox/sliver
- Affected
- >=1.5.0
- Fixed in
- No fix released
Sliver Allows Authenticated Operator-to-Server Remote Code Execution in github.com/bishopfox/sliver
- Affected
- >=1.5.40
- Fixed in
- No fix released
Fixed within 1.6.x, affecting earlier releases
Sliver Vulnerable to Website Path Traversal / Arbitrary File Read (Authenticated) in github.com/bishopfox/sliver
- Affected
- <1.6.11
- Fixed in
- 1.6.11
Sliver Vulnerable to Website Path Traversal / Arbitrary File Read (Authenticated)
- Affected
- <1.6.11
- Fixed in
- 1.6.11
Every github.com/bishopfox/sliver 1.6.x release
Affected: 1.6.0 to 1.6.11. Latest github.com/bishopfox/sliver: 1.7.9.
| Version | Known advisories |
|---|---|
| github.com/bishopfox/sliver 1.6.11 | CVE-2026-77622, CVE-2026-34227, GO-2026-4899, CVE-2026-34227, GHSA-c279-989m-238f, CVE-2026-32941, CVE-2026-32941, CVE-2026-29781, CVE-2026-29781, GO-2026-4548, GHSA-2phg-qgmm-r638, CVE-2026-25791, CVE-2026-25791, GO-2026-4280, CVE-2024-41111 |
| github.com/bishopfox/sliver 1.6.10 | CVE-2026-77622, CVE-2026-34227, GO-2026-4899, CVE-2026-34227, GHSA-c279-989m-238f, CVE-2026-32941, CVE-2026-32941, CVE-2026-29781, CVE-2026-29781, GO-2026-4548, GHSA-2phg-qgmm-r638, CVE-2026-25760, CVE-2026-25791, CVE-2026-25791, CVE-2026-25760, GO-2026-4280, CVE-2024-41111 |
| github.com/bishopfox/sliver 1.6.9 | CVE-2026-77622, CVE-2026-34227, GO-2026-4899, CVE-2026-34227, GHSA-c279-989m-238f, CVE-2026-32941, CVE-2026-32941, CVE-2026-29781, CVE-2026-29781, GO-2026-4548, GHSA-2phg-qgmm-r638, CVE-2026-25760, CVE-2026-25791, CVE-2026-25791, CVE-2026-25760, GO-2026-4280, CVE-2024-41111 |
| github.com/bishopfox/sliver 1.6.8 | CVE-2026-77622, CVE-2026-34227, GO-2026-4899, CVE-2026-34227, GHSA-c279-989m-238f, CVE-2026-32941, CVE-2026-32941, CVE-2026-29781, CVE-2026-29781, GO-2026-4548, GHSA-2phg-qgmm-r638, CVE-2026-25760, CVE-2026-25791, CVE-2026-25791, CVE-2026-25760, GO-2026-4280, CVE-2024-41111 |
| github.com/bishopfox/sliver 1.6.7 | CVE-2026-77622, CVE-2026-34227, GO-2026-4899, CVE-2026-34227, GHSA-c279-989m-238f, CVE-2026-32941, CVE-2026-32941, CVE-2026-29781, CVE-2026-29781, GO-2026-4548, GHSA-2phg-qgmm-r638, CVE-2026-25760, CVE-2026-25791, CVE-2026-25791, CVE-2026-25760, GO-2026-4280, CVE-2024-41111 |
| github.com/bishopfox/sliver 1.6.6 | CVE-2026-77622, CVE-2026-34227, GO-2026-4899, CVE-2026-34227, GHSA-c279-989m-238f, CVE-2026-32941, CVE-2026-32941, CVE-2026-29781, CVE-2026-29781, GO-2026-4548, GHSA-2phg-qgmm-r638, CVE-2026-25760, CVE-2026-25791, CVE-2026-25791, CVE-2026-25760, GO-2026-4280, CVE-2024-41111 |
| github.com/bishopfox/sliver 1.6.5 | CVE-2026-77622, CVE-2026-34227, GO-2026-4899, CVE-2026-34227, GHSA-c279-989m-238f, CVE-2026-32941, CVE-2026-32941, CVE-2026-29781, CVE-2026-29781, GO-2026-4548, GHSA-2phg-qgmm-r638, CVE-2026-25760, CVE-2026-25791, CVE-2026-25791, CVE-2026-25760, GO-2026-4280, CVE-2024-41111 |
| github.com/bishopfox/sliver 1.6.4 | CVE-2026-77622, CVE-2026-34227, GO-2026-4899, CVE-2026-34227, GHSA-c279-989m-238f, CVE-2026-32941, CVE-2026-32941, CVE-2026-29781, CVE-2026-29781, GO-2026-4548, GHSA-2phg-qgmm-r638, CVE-2026-25760, CVE-2026-25791, CVE-2026-25791, CVE-2026-25760, GO-2026-4280, CVE-2024-41111 |
| github.com/bishopfox/sliver 1.6.3 | CVE-2026-77622, CVE-2026-34227, GO-2026-4899, CVE-2026-34227, GHSA-c279-989m-238f, CVE-2026-32941, CVE-2026-32941, CVE-2026-29781, CVE-2026-29781, GO-2026-4548, GHSA-2phg-qgmm-r638, CVE-2026-25760, CVE-2026-25791, CVE-2026-25791, CVE-2026-25760, GO-2026-4280, CVE-2024-41111 |
| github.com/bishopfox/sliver 1.6.2 | CVE-2026-77622, CVE-2026-34227, GO-2026-4899, CVE-2026-34227, GHSA-c279-989m-238f, CVE-2026-32941, CVE-2026-32941, CVE-2026-29781, CVE-2026-29781, GO-2026-4548, GHSA-2phg-qgmm-r638, CVE-2026-25760, CVE-2026-25791, CVE-2026-25791, CVE-2026-25760, GO-2026-4280, CVE-2024-41111 |
| github.com/bishopfox/sliver 1.6.1 | CVE-2026-77622, CVE-2026-34227, GO-2026-4899, CVE-2026-34227, GHSA-c279-989m-238f, CVE-2026-32941, CVE-2026-32941, CVE-2026-29781, CVE-2026-29781, GO-2026-4548, GHSA-2phg-qgmm-r638, CVE-2026-25760, CVE-2026-25791, CVE-2026-25791, CVE-2026-25760, GO-2026-4280, CVE-2024-41111 |
| github.com/bishopfox/sliver 1.6.0 | CVE-2026-77622, CVE-2026-34227, GO-2026-4899, CVE-2026-34227, GHSA-c279-989m-238f, CVE-2026-32941, CVE-2026-32941, CVE-2026-29781, CVE-2026-29781, GO-2026-4548, GHSA-2phg-qgmm-r638, CVE-2026-25760, CVE-2026-25791, CVE-2026-25791, CVE-2026-25760, GO-2026-4280, CVE-2024-41111 |
Which of your client projects are still on github.com/bishopfox/sliver 1.6?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/bishopfox/sliver version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/bishopfox/sliver versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.