# CVE-2025-27093: Sliver does not restricted traffic between Wireguard clients.

> Sliver C2 framework allows unrestricted traffic between Wireguard clients, enabling implants to attack operators or access port forwards.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Oct 2025
- **Updated:** 29 Oct 2025
- **Also known as:** GHSA-q8j9-34qf-7vq7, GO-2025-4079

## What is CVE-2025-27093?

CVE-2025-27093 is a medium-severity missing authorization vulnerability in BishopFox sliver, published on 28 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Sliver is a command and control framework that uses a custom Wireguard netstack. In versions 1.5.43 and earlier, and in development version 1.6.0-dev, the netstack does not limit traffic between Wireguard clients. This allows clients to communicate with each other unrestrictedly, potentially enabling leaked or recovered keypairs to be used to attack operators or allowing port forwardings to be accessible from other implants.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-27093?

5 open source packages ship an affected version, including github.com/bishopfox/sliver and github.com/BishopFox/sliver.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/bishopfox/sliver` | Go | All versions | 1.5.44 |
| `github.com/bishopfox/sliver` | Go | All versions | 1.5.44 |
| `github.com/bishopfox/sliver` | Go | All versions | 1.5.44 |
| `github.com/BishopFox/sliver` | Go | All versions | 1.5.44 |
| `github.com/BishopFox/sliver` | Go | All versions | 1.5.44 |

## How do I fix CVE-2025-27093?

Upgrade github.com/bishopfox/sliver to 1.5.44 or later.

## Is CVE-2025-27093 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27093 and fix it if it is affected.

What it is: CVE-2025-27093 is a medium-severity missing authorization vulnerability in BishopFox sliver, published on 28 Oct 2025. An attacker can exploit it over the internet without logging in, 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-2025-27093 exists.

Affected packages and fixed versions:
- github.com/bishopfox/sliver (Go): affected all versions; fixed in 1.5.44
- github.com/bishopfox/sliver (Go): affected all versions; fixed in 1.5.44
- github.com/bishopfox/sliver (Go): affected all versions; fixed in 1.5.44
- github.com/BishopFox/sliver (Go): affected all versions; fixed in 1.5.44
- github.com/BishopFox/sliver (Go): affected all versions; fixed in 1.5.44

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-2025-27093/ (Markdown: https://insights.sbomify.com/CVE-2025-27093/index.md)
```

## Sources

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

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