# CVE-2026-102507: Sliver 1.7.7 Denial of Service via PE Parser Slice Bounds in Operator RPC

> A hostile implant can crash the Sliver teamserver by sending malformed download responses, causing a denial of service for all operators.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-57xm-mfg7-58xm

## What is CVE-2026-102507?

CVE-2026-102507 is a medium-severity denial of service vulnerability in BishopFox sliver, published on 29 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Sliver C2 framework version 1.7.7 and earlier contains an unhandled panic vulnerability in the operator gRPC handler that allows an attacker controlling a compromised implant to crash the entire teamserver by returning a malformed or empty Download response. Attackers can send zero-length or 1-3 byte data payloads through a hostile implant session to trigger an out-of-bounds slice access in the vendored Binject library's BinaryMagic function, which propagates unrecovered through the operator gRPC interceptor chain and terminates the server process, affecting all connected operators.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-102507?


## How do I fix CVE-2026-102507?

No fix has been published for CVE-2026-102507 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102507 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102507 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102507 and fix it if it is affected.

What it is: CVE-2026-102507 is a medium-severity denial of service vulnerability in BishopFox sliver, published on 29 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102507 exists.

Affected product: BishopFox sliver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102507/ (Markdown: https://insights.sbomify.com/CVE-2026-102507/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102507
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102507
- OSV: https://osv.dev/vulnerability/CVE-2026-102507

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102507/
Summaries are generated and may contain mistakes; the official description above is the record.