How severe is GHSA-7jx5-9fjg-hp4m?

GHSA-7jx5-9fjg-hp4m has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-7jx5-9fjg-hp4m?

GHSA-7jx5-9fjg-hp4m affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-7jx5-9fjg-hp4m?

Update openclaw to 2026.2.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7jx5-9fjg-hp4m is resolved across your whole dependency graph.

How do I detect GHSA-7jx5-9fjg-hp4m 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-7jx5-9fjg-hp4m 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-7jx5-9fjg-hp4m?

O3 pinpoints whether GHSA-7jx5-9fjg-hp4m 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-7jx5-9fjg-hp4m actively exploited in the wild?

No public exploit code has been indexed for GHSA-7jx5-9fjg-hp4m 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 GHSA-7jx5-9fjg-hp4m?

GHSA-7jx5-9fjg-hp4m has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th 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 GHSA-7jx5-9fjg-hp4m?

GHSA-7jx5-9fjg-hp4m is classified as CWE-807 (CWE-807). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-7jx5-9fjg-hp4m published, and has it been updated?

GHSA-7jx5-9fjg-hp4m was published on February 27, 2026 and was last updated on March 30, 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-7jx5-9fjg-hp4m

MEDIUM

OpenClaw ACP client has permission auto-approval bypass via untrusted tool metadata

Also known asCVE-2026-32898

Published

Feb 27, 2026

Updated

Mar 30, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk17th percentile+0.23%

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.

Blast Radius

1 pkg affected

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

openclawnpm

4.4Mdownloads / week

Description

Vulnerability Summary

The OpenClaw ACP client could auto-approve tool calls based on untrusted metadata and permissive name heuristics. A malicious or compromised ACP tool invocation could bypass expected interactive approval prompts for read-class operations.

Affected Packages / Versions

Package: npm openclaw
Affected published versions: <= 2026.2.22-2 (latest published as of February 24, 2026 is 2026.2.22-2)
Patched in code on main: 2026.2.23 (released)

Technical Details

Permission classification trusted incoming toolCall.kind and heuristic name matching.
Non-core read-like names and spoofed kind metadata could reach auto-approve paths.
read operations were not scoped strongly enough to cwd in all metadata/title forms.

Fix

Require trusted core tool IDs for auto-approval and ignore untrusted toolCall.kind as an authorization source.
Scope read auto-approval to cwd-resolved paths.
Add stricter tool-name validation and regression coverage for spoofed kind and non-core read-like names.

Affected Functions

resolvePermissionRequest
resolveToolNameForPermission
shouldAutoApproveToolCall

Fix Commit(s)

12cc754332f9a7c92e158ce7644aa22df79c0904
63dcd28ae0be2de1c75af09cc81841cebeec068f

Found using MCPwner

Thanks @nedlir for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.23

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.2.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7jx5-9fjg-hp4m 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-7jx5-9fjg-hp4m 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-7jx5-9fjg-hp4m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Vulnerability Summary The OpenClaw ACP client could auto-approve tool calls based on untrusted metadata and permissive name heuristics. A malicious or compromised ACP tool invocation could bypass expected interactive approval prompts for read-class operations. ## Affected Packages / Versions - Package: npm `openclaw` - Affected published versions: `<= 2026.2.22-2` (latest published as of February 24, 2026 is `2026.2.22-2`) - Patched in code on `main`: `2026.2.23` (released) ## Technical Details - Permission classification trusted incoming `toolCall.kind` and heuristic name matching. -

O3 Security · Impact-Aware SCA

Is GHSA-7jx5-9fjg-hp4m in your dependencies?

O3 detects GHSA-7jx5-9fjg-hp4m 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