How severe is GHSA-w67g-5rqw-f597?

No CVSS score has been assigned to GHSA-w67g-5rqw-f597 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w67g-5rqw-f597?

GHSA-w67g-5rqw-f597 affects the following packages: github.com/gorilla/websocket (Go). Ecosystems affected: Go.

How do I fix GHSA-w67g-5rqw-f597?

Update github.com/gorilla/websocket to 1.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w67g-5rqw-f597 is resolved across your whole dependency graph.

How do I detect GHSA-w67g-5rqw-f597 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gorilla/websocket. 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-w67g-5rqw-f597 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-w67g-5rqw-f597?

O3 pinpoints whether GHSA-w67g-5rqw-f597 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-w67g-5rqw-f597 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w67g-5rqw-f597 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.

When was GHSA-w67g-5rqw-f597 published, and has it been updated?

GHSA-w67g-5rqw-f597 was published on August 24, 2026 and was last updated on August 26, 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

Not in CISA KEV

GHSA-w67g-5rqw-f597

Fix: gorilla/websocket@d67f418

GHSA-w67g-5rqw-f597 is a security vulnerability in github.com/gorilla/websocket. O3 Security confirms whether GHSA-w67g-5rqw-f597 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Gorilla WebSocket Uses Cryptographically Weak PRNG for WebSocket Mask Key

Also known asGO-2026-6278

Published

Aug 24, 2026

Updated

Aug 26, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 26, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/gorilla/websocket

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

gorilla/websocket used math/rand (cryptographically weak pseudo-random number generator) to generate WebSocket frame mask keys prior to commit d67f4185. WebSocket masking keys MUST be unpredictable to prevent frame content injection attacks. math/rand produces deterministic output when seeded with a known value, enabling an attacker to predict or recover mask keys and inject content into WebSocket connections.

Type: Use of Cryptographically Weak Pseudo-Random Number Generator Fix: Replaced math/rand with crypto/rand (commit d67f4185, released in v1.5.3) Credit: bounty-hunter v6.0 silent-fix detection

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/gorilla/websocket`	all versions	1.5.3

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/gorilla/websocket. 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/gorilla/websocket to 1.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w67g-5rqw-f597 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-w67g-5rqw-f597 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-w67g-5rqw-f597. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

gorilla/websocket used `math/rand` (cryptographically weak pseudo-random number generator) to generate WebSocket frame mask keys prior to commit d67f4185. WebSocket masking keys MUST be unpredictable to prevent frame content injection attacks. math/rand produces deterministic output when seeded with a known value, enabling an attacker to predict or recover mask keys and inject content into WebSocket connections. **Type:** Use of Cryptographically Weak Pseudo-Random Number Generator **Fix:** Replaced math/rand with crypto/rand (commit d67f4185, released in v1.5.3) **Credit:** bounty-hunter v6.

O3 Security · Impact-Aware SCA

Is GHSA-w67g-5rqw-f597 in your dependencies?

O3 detects GHSA-w67g-5rqw-f597 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