How severe is GHSA-wxrw-gvg8-fqjp?

GHSA-wxrw-gvg8-fqjp has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-wxrw-gvg8-fqjp?

GHSA-wxrw-gvg8-fqjp affects the following packages: github.com/bishopfox/sliver (Go). Ecosystems affected: Go.

How do I fix GHSA-wxrw-gvg8-fqjp?

Update github.com/bishopfox/sliver to 1.6.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wxrw-gvg8-fqjp is resolved across your whole dependency graph.

How do I detect GHSA-wxrw-gvg8-fqjp in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bishopfox/sliver. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-wxrw-gvg8-fqjp if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-wxrw-gvg8-fqjp?

O3 pinpoints whether GHSA-wxrw-gvg8-fqjp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-wxrw-gvg8-fqjp actively exploited in the wild?

No public exploit code has been indexed for GHSA-wxrw-gvg8-fqjp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-wxrw-gvg8-fqjp?

GHSA-wxrw-gvg8-fqjp has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-wxrw-gvg8-fqjp?

GHSA-wxrw-gvg8-fqjp is classified as Missing Authentication (CWE-306), Uncontrolled Resource Consumption (CWE-400). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-wxrw-gvg8-fqjp published, and has it been updated?

GHSA-wxrw-gvg8-fqjp was published on February 6, 2026 and was last updated on February 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-wxrw-gvg8-fqjp

HIGH

Sliver has DNS C2 OTP Bypass that Allows Unauthenticated Session Flooding and Denial of Service

Also known asCVE-2026-25791GO-2026-4466

Published

Feb 6, 2026

Updated

Feb 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk32th percentile+0.38%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹github.com/bishopfox/sliver

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The DNS C2 listener accepts unauthenticated TOTP bootstrap messages and allocates server-side DNS sessions without validating OTP values, even when EnforceOTP is enabled. Because sessions are stored without a cleanup/expiry path in this flow, an unauthenticated remote actor can repeatedly create sessions and drive memory exhaustion.

Vulnerable Component

server/c2/dns.go:84-90 (EnforceOTP stored but not enforced in bootstrap)
server/c2/dns.go:378-390 (TOTP requests routed directly to bootstrap)
server/c2/dns.go:490-521 (handleHello allocates session without OTP validation)
server/c2/dns.go:495 (sessions.Store with no lifecycle control in this path)
client/command/jobs/dns.go:46-52 (operator-facing EnforceOTP control implies auth gate)
implant/sliver/transports/dnsclient/dnsclient.go:896-900 (otpMsg sends TOTP with ID=0)
protobuf/dnspb/dns.proto:22 (documents TOTP in ID field)

Attack Vector

Network-accessible DNS listener
No authentication required
Low-complexity repeated DNS query loop
Trigger path: DNSMessageType_TOTP bootstrap handling

Proof of Concept

Preconditions

DNS listener is reachable
DNS C2 job is active

Reproduction Steps

Send repeated DNS queries with a minimal protobuf message of type TOTP.
Observe repeated session allocation/issuance behavior.
Continue requests to increase active in-memory session state.

Example

while true; do
  dig +short @<DNS_C2_IP> baa8.<parent-domain> A >/dev/null
done

baa8 is a base32 payload for a minimal TOTP-type protobuf message.

Observable Indicators

Repeated bootstrap/session-allocation log entries from handleHello
Rising memory usage in the Sliver server process
Service slowdown or instability under sustained request volume

Impact

Unauthenticated remote denial of service (availability)
Resource exhaustion through unbounded session growth in DNS bootstrap path
Estimated CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (7.5 High)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/bishopfox/sliver`	all versions	1.6.12

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bishopfox/sliver. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/bishopfox/sliver to 1.6.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wxrw-gvg8-fqjp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-wxrw-gvg8-fqjp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wxrw-gvg8-fqjp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary The DNS C2 listener accepts unauthenticated `TOTP` bootstrap messages and allocates server-side DNS sessions without validating OTP values, even when `EnforceOTP` is enabled. Because sessions are stored without a cleanup/expiry path in this flow, an unauthenticated remote actor can repeatedly create sessions and drive memory exhaustion. ## Vulnerable Component - `server/c2/dns.go:84-90` (`EnforceOTP` stored but not enforced in bootstrap) - `server/c2/dns.go:378-390` (`TOTP` requests routed directly to bootstrap) - `server/c2/dns.go:490-521` (`handleHello` allocates session without

O3 Security · Impact-Aware SCA

Is GHSA-wxrw-gvg8-fqjp in your dependencies?

O3 detects GHSA-wxrw-gvg8-fqjp across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10

CVSS v3 base score

Vector breakdown

AV:Attack Vector

Network

AC:Attack Complexity

Low

PR:Privileges Required

None

UI:User Interaction

None

S:Scope

Unchanged

C:Confidentiality

None

I:Integrity

None

A:Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

CWE Classification

CWE-306Missing Authentication CWE-400Uncontrolled Resource Consumption

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

sliver

6.0/10

Code-Review5/10

Maintained10/10

Branch-Protection8/10

Assessed Jun 22, 2026

Timeline

Disclosed

Feb 6, 2026

Last updated

Feb 19, 2026

Identifiers

GHSA-wxrw-gvg8-fqjp

GO-2026-4466

References

Advisorynvd.nist.gov Webgithub.com Webgithub.com Webgithub.com Packagegithub.com

Data from OSV.dev, enriched by O3 Security. Refreshed hourly.

GHSA-wxrw-gvg8-fqjp

EPSS Exploitation Probability

Blast Radius

Description

Summary

Vulnerable Component

Attack Vector

Proof of Concept

Preconditions

Reproduction Steps

Example

Observable Indicators

Impact

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-wxrw-gvg8-fqjp in your dependencies?