How severe is GHSA-92jp-89mq-4374?

No CVSS score has been assigned to GHSA-92jp-89mq-4374 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-92jp-89mq-4374?

GHSA-92jp-89mq-4374 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-92jp-89mq-4374?

Update openclaw to 2026.4.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-92jp-89mq-4374 is resolved across your whole dependency graph.

How do I detect GHSA-92jp-89mq-4374 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. 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-92jp-89mq-4374 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-92jp-89mq-4374?

O3 pinpoints whether GHSA-92jp-89mq-4374 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-92jp-89mq-4374 actively exploited in the wild?

No public exploit code has been indexed for GHSA-92jp-89mq-4374 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-92jp-89mq-4374 published, and has it been updated?

GHSA-92jp-89mq-4374 was published on April 17, 2026 and was last updated on April 17, 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

GHSA-92jp-89mq-4374

OpenClaw: Sandbox noVNC helper route exposed interactive browser session credentials

Published

Apr 17, 2026

Updated

Apr 17, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm

4.3Mdownloads / week

Description

Summary

Sandbox noVNC helper route exposed interactive browser session credentials.

Affected Packages / Versions

Package: openclaw
Ecosystem: npm
Affected versions: >= 2026.2.21 < 2026.4.10
Patched versions: >= 2026.4.10

Impact

The sandbox noVNC helper route could be reached without the intended bridge authentication, exposing an interactive browser session surface.

Technical Details

The fix gates the sandbox noVNC helper route behind bridge authentication.

Fix

The issue was fixed in #63882. The first stable tag containing the fix is v2026.4.10, and [email protected] includes the fix.

Fix Commit(s)

8dfbf3268bd224b7377d1ecca77a445100746085
PR: #63882

Release Process Note

Users should upgrade to openclaw 2026.4.10 or newer. The latest npm release, 2026.4.14, already includes the fix.

Credits

Thanks to @zsxsoft, with sponsorship from @KeenSecurityLab and @qclawer for reporting this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.2.21&&< 2026.4.10	2026.4.10

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. 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 openclaw to 2026.4.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-92jp-89mq-4374 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-92jp-89mq-4374 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-92jp-89mq-4374. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Sandbox noVNC helper route exposed interactive browser session credentials. ## Affected Packages / Versions - Package: `openclaw` - Ecosystem: npm - Affected versions: `>= 2026.2.21 < 2026.4.10` - Patched versions: `>= 2026.4.10` ## Impact The sandbox noVNC helper route could be reached without the intended bridge authentication, exposing an interactive browser session surface. ## Technical Details The fix gates the sandbox noVNC helper route behind bridge authentication. ## Fix The issue was fixed in #63882. The first stable tag containing the fix is `v2026.4.10`, and `ope

O3 Security · Impact-Aware SCA

Is GHSA-92jp-89mq-4374 in your dependencies?

O3 detects GHSA-92jp-89mq-4374 across npm 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