How severe is GHSA-9hjh-fr4f-gxc4?

No CVSS score has been assigned to GHSA-9hjh-fr4f-gxc4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9hjh-fr4f-gxc4?

GHSA-9hjh-fr4f-gxc4 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-9hjh-fr4f-gxc4?

No patched version of openclaw has shipped for GHSA-9hjh-fr4f-gxc4 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-9hjh-fr4f-gxc4 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-9hjh-fr4f-gxc4 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-9hjh-fr4f-gxc4?

O3 pinpoints whether GHSA-9hjh-fr4f-gxc4 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-9hjh-fr4f-gxc4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9hjh-fr4f-gxc4 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 type of vulnerability is GHSA-9hjh-fr4f-gxc4?

GHSA-9hjh-fr4f-gxc4 is classified as CWE-648 (CWE-648). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9hjh-fr4f-gxc4 published, and has it been updated?

GHSA-9hjh-fr4f-gxc4 was published on March 27, 2026 and was last updated on April 10, 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

GHSA-9hjh-fr4f-gxc4

Fix: openclaw/openclaw@d3d8e31

GHSA-9hjh-fr4f-gxc4 is a CWE-648 vulnerability in openclaw. O3 Security confirms whether GHSA-9hjh-fr4f-gxc4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Gateway Backend Reconnect lets Non-Admin Operator Scopes Self-Claim operator.admin

Also known asCVE-2026-35663

Published

Mar 27, 2026

Updated

Apr 10, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

openclawnpm

3.2Mdownloads / week

Description

Summary

Gateway Backend Reconnect lets Non-Admin Operator Scopes Self-Claim operator.admin

Affected Packages / Versions

Package: openclaw
Affected versions: <= 2026.3.24
First patched version: 2026.3.25
Latest published npm version at verification time: 2026.3.24

Details

Backend-labeled reconnects could previously self-request broader scopes and bypass pairing, allowing non-admin operators to reconnect as operator.admin. Commit d3d8e316bd819d3c7e34253aeb7eccb2510f5f48 removes the backend self-pairing skip and requires pairing when requested scopes exceed the approved baseline.

Verified vulnerable on tag v2026.3.24 and fixed on main by commit d3d8e316bd819d3c7e34253aeb7eccb2510f5f48.

Fix Commit(s)

d3d8e316bd819d3c7e34253aeb7eccb2510f5f48

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	No fix

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.
Remediation status
No patched version of openclaw has shipped for GHSA-9hjh-fr4f-gxc4 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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-9hjh-fr4f-gxc4 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-9hjh-fr4f-gxc4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Gateway Backend Reconnect lets Non-Admin Operator Scopes Self-Claim operator.admin ## Affected Packages / Versions - Package: `openclaw` - Affected versions: `<= 2026.3.24` - First patched version: `2026.3.25` - Latest published npm version at verification time: `2026.3.24` ## Details Backend-labeled reconnects could previously self-request broader scopes and bypass pairing, allowing non-admin operators to reconnect as `operator.admin`. Commit `d3d8e316bd819d3c7e34253aeb7eccb2510f5f48` removes the backend self-pairing skip and requires pairing when requested scopes exceed the a

O3 Security · Impact-Aware SCA

Is GHSA-9hjh-fr4f-gxc4 in your dependencies?

O3 detects GHSA-9hjh-fr4f-gxc4 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