How severe is CVE-2026-32062?

No CVSS score has been assigned to CVE-2026-32062 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-32062?

CVE-2026-32062 affects the following packages: openclaw (npm), @openclaw/voice-call (npm). Ecosystems affected: npm.

How do I fix CVE-2026-32062?

Update openclaw to 2026.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32062 is resolved across your whole dependency graph.

How do I detect CVE-2026-32062 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-32062 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 CVE-2026-32062?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-32062 can be triaged on real exposure rather than presence alone.

Is CVE-2026-32062 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-32062 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 CVE-2026-32062?

CVE-2026-32062 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 37th 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 CVE-2026-32062?

CVE-2026-32062 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-32062 published, and has it been updated?

CVE-2026-32062 was published on March 11, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-32062 — openclaw

Fix: openclaw/openclaw@1d8968c

CVE-2026-32062 is a CWE-770 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw 2026.2.21-2 < 2026.2.22 - Unauthenticated WebSocket Resource Exhaustion via Media Stream

Also known asGHSA-mfg5-7q5g-f37j

Published

Mar 11, 2026

Updated

Aug 12, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-32062.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

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.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

2.5Mdownloads / week

@openclaw/voice-callnpm

3Kdownloads / week

Description

Summary

@openclaw/voice-call (and the bundled copy shipped in openclaw) accepted media-stream WebSocket upgrades before stream validation. In reachable deployments, unauthenticated pre-start sockets could be held open and increase resource pressure.

Affected Packages / Versions

openclaw (npm): vulnerable <= 2026.2.21-2, patched in 2026.2.22.
@openclaw/voice-call (npm): vulnerable <= 2026.2.21, patched in 2026.2.22.

Technical Details

Before this fix, the voice-call media-stream path upgraded sockets first and ran shouldAcceptStream() after a later start frame. This created a pre-auth window where remote clients could hold idle sockets without call/token validation.

Impact

Availability risk in deployments where the media-stream endpoint is reachable and streaming is enabled. Under sustained abuse, this could consume connection-related resources and degrade service for legitimate streams.

Remediation

The fix adds layered controls in the media-stream path:

strict pre-start timeout (close sockets that do not send a valid start frame quickly)
global pending-connection cap
per-IP pending-connection cap
total open media-stream connection cap
safer upgrade-path parsing in the webhook server

Fix Commit(s)

1d8968c8a821ff1a05c294a1846b3bcb6f343794

Release Process Note

patched_versions is pre-set to 2026.2.22 so this advisory is ready to publish once npm [email protected] and @openclaw/[email protected] are released.

OpenClaw thanks @jiseoung for reporting.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.22`npm install openclaw@2026.2.22`
📦npm	`@openclaw/voice-call`	all versions	2026.2.22`npm install @openclaw/voice-call@2026.2.22`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32062 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-32062 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2026-32062. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary `@openclaw/voice-call` (and the bundled copy shipped in `openclaw`) accepted media-stream WebSocket upgrades before stream validation. In reachable deployments, unauthenticated pre-start sockets could be held open and increase resource pressure. ### Affected Packages / Versions - `openclaw` (npm): vulnerable `<= 2026.2.21-2`, patched in `2026.2.22`. - `@openclaw/voice-call` (npm): vulnerable `<= 2026.2.21`, patched in `2026.2.22`. ### Technical Details Before this fix, the voice-call media-stream path upgraded sockets first and ran `shouldAcceptStream()` after a later `start` fra

O3 Security · Impact-Aware SCA

Is CVE-2026-32062 in your dependencies?

O3 Security finds CVE-2026-32062 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works