Sliver Allows Authenticated Operator-to-Server Remote Code Execution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-41111: 0.71% estimated exploitation activity in the next 30 days; percentile 53.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Description Sliver version 1.6.0 (prerelease) is vulnerable to RCE on the teamserver by a low-privileged "operator" user. The RCE is as the system root user. Impact As described in a past issue, "there is a clear security boundary between the operator and server, an operator should not inherently be able to run commands or code on the server." An operator who exploited this vulnerability would be able to view all console logs, kick all other operators, view and modify files stored on the server, and ultimately delete the server. Reproduction First configure the Sliver server in multiplayer mode and add an operator profile. Next, compile a slightly older version of the Sliver client. The commit after 5016fb8d updates the Cobra command-line parsing library in the Sliver client to strictly validate command flags. The latest server version is targeted: The exploit uses a command injection in the generate msf-stager to inject the --out flag to msfvenom. We overwrite Sliver's own go binary…

Published by the source

18 Jul 2024, 20:23 UTC

Last modified by the source

2 Aug 2024, 23:10 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hc5w-gxxr-w8x8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-41111

Advisory: Sliver Allows Authenticated Operator-to-Server Remote Code Execution
IDs: CVE-2024-41111, GHSA-hc5w-gxxr-w8x8
Record: https://patchnext.com/advisories/cve-2024-41111 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/bishopfox/sliver 1.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/bishopfox/sliver: affected >= 1.5.40, <= 1.6.0-dev; fixed in 1.6.0

## Suggested inspection (read-only)
- Go github.com/bishopfox/sliver: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/bishopfox/sliver.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hc5w-gxxr-w8x8 (GitHub-reviewed advisory GHSA-hc5w-gxxr-w8x8 lists affected ranges: Go github.com/bishopfox/sliver >=1.5.40 <=1.6.0-dev)

Commands are suggestions: review each one before running it.