How severe is GHSA-9wqx-g2cw-vc7r?

No CVSS score has been assigned to GHSA-9wqx-g2cw-vc7r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9wqx-g2cw-vc7r?

GHSA-9wqx-g2cw-vc7r affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-9wqx-g2cw-vc7r?

No patched version of openclaw has shipped for GHSA-9wqx-g2cw-vc7r 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-9wqx-g2cw-vc7r 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-9wqx-g2cw-vc7r 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-9wqx-g2cw-vc7r?

O3 pinpoints whether GHSA-9wqx-g2cw-vc7r 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-9wqx-g2cw-vc7r actively exploited in the wild?

No public exploit code has been indexed for GHSA-9wqx-g2cw-vc7r 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-9wqx-g2cw-vc7r?

GHSA-9wqx-g2cw-vc7r is classified as CWE-288 (CWE-288). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9wqx-g2cw-vc7r published, and has it been updated?

GHSA-9wqx-g2cw-vc7r 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

GHSA-9wqx-g2cw-vc7r

GHSA-9wqx-g2cw-vc7r is a CWE-288 vulnerability in openclaw. O3 Security confirms whether GHSA-9wqx-g2cw-vc7r is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: Matrix Verification Notices Bypass Matrix DM Policy and Reply to Unpaired DM Peers

Also known asCVE-2026-35647

Published

Mar 27, 2026

Updated

Apr 10, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Blast Radius

1 pkg affected

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

openclawnpm

3.2Mdownloads / week

Description

Summary

Matrix Verification Notices Bypass Matrix DM Policy and Reply to Unpaired DM Peers

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

Matrix verification notices previously bypassed DM access checks and could reply to peers that were unpaired or otherwise outside the allowed DM policy. Commit 2383daf5c4a4e08d9553e0e949552ad755ef9ec2 gates verification notices on DM access before sending.

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

Fix Commit(s)

2383daf5c4a4e08d9553e0e949552ad755ef9ec2

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-9wqx-g2cw-vc7r 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-9wqx-g2cw-vc7r 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-9wqx-g2cw-vc7r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Matrix Verification Notices Bypass Matrix DM Policy and Reply to Unpaired DM Peers ## 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 Matrix verification notices previously bypassed DM access checks and could reply to peers that were unpaired or otherwise outside the allowed DM policy. Commit `2383daf5c4a4e08d9553e0e949552ad755ef9ec2` gates verification notices on DM access before sending. Verified vulnerable on tag `v2026.3.24

O3 Security · Impact-Aware SCA

Is GHSA-9wqx-g2cw-vc7r in your dependencies?

O3 detects GHSA-9wqx-g2cw-vc7r 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