Quick answers
- Is CVE-2026-102507 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102507 being exploited in the wild.
- How severe is CVE-2026-102507?
- Medium severity, with a CVSS score of 5.7, published 29 September 2026.
- Which products and versions are affected?
- Bishopfox Sliver 1.1.0 through 1.7.7.
- Is there a fix for CVE-2026-102507?
- 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.
- How is CVE-2026-102507 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-102507?
- Check whether you run Bishopfox Sliver 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.
Technical details
An unhandled panic occurs in the operator gRPC handler when the backdoor command feeds hostile Download response data directly to the vendored Binject PE parser without validation. A zero-length or 1-3 byte payload triggers an out-of-bounds slice access in BinaryMagic, which panics. The panic propagates through an unprotected gRPC interceptor chain and terminates the entire teamserver process, affecting all connected operators and implants. The attack requires control of a compromised implant with valid mTLS credentials.
Affected products
- BishopFox Sliver 1.1.0 through 1.7.7
Timeline
- 2026-09-29: disclosed: Public disclosure via GitHub PoC
- 2026-09-17: other: Vendor notified; closed report as out-of-scope