How severe is GHSA-q3jj-46pq-826r?

No CVSS score has been assigned to GHSA-q3jj-46pq-826r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q3jj-46pq-826r?

GHSA-q3jj-46pq-826r affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-q3jj-46pq-826r?

Update openclaw to 2026.4.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q3jj-46pq-826r is resolved across your whole dependency graph.

How do I detect GHSA-q3jj-46pq-826r 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-q3jj-46pq-826r 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-q3jj-46pq-826r?

O3 pinpoints whether GHSA-q3jj-46pq-826r 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-q3jj-46pq-826r actively exploited in the wild?

No public exploit code has been indexed for GHSA-q3jj-46pq-826r 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-q3jj-46pq-826r published, and has it been updated?

GHSA-q3jj-46pq-826r was published on May 4, 2026 and was last updated on May 19, 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-q3jj-46pq-826r

GHSA-q3jj-46pq-826r is a security vulnerability in openclaw. O3 Security confirms whether GHSA-q3jj-46pq-826r is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw's ACP child sessions inherit subagent security envelope constraints

Also known asCVE-2026-44997

Published

May 4, 2026

Updated

May 19, 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

3.1Mdownloads / week

Description

Summary

ACP child sessions inherit subagent security envelope constraints.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.4.21
Fixed version: 2026.4.22

Impact

A restricted subagent spawning an ACP child session could fail to carry forward subagent-only constraints such as depth, child-count limits, control scope, or target-agent restrictions.

Fix

ACP spawn now resolves and persists child subagent envelope fields, enforces maximum depth and active-child caps, and applies the inherited control scope to child ACP sessions.

Fix Commit(s)

31160dc069b7cc5d833b39c53736a41ad3befda2

Verification

The fix commit is contained in the public v2026.4.22 tag.
[email protected] is published on npm and the compiled package contains the fix.
Focused regression coverage for this path passed before publication.

OpenClaw thanks @zsxsoft, @qclawer, and @KeenSecurityLab for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.4.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. 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.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q3jj-46pq-826r 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-q3jj-46pq-826r 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-q3jj-46pq-826r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary ACP child sessions inherit subagent security envelope constraints. ## Affected Packages / Versions - Package: openclaw (npm) - Affected versions: <= 2026.4.21 - Fixed version: 2026.4.22 ## Impact A restricted subagent spawning an ACP child session could fail to carry forward subagent-only constraints such as depth, child-count limits, control scope, or target-agent restrictions. ## Fix ACP spawn now resolves and persists child subagent envelope fields, enforces maximum depth and active-child caps, and applies the inherited control scope to child ACP sessions. ## Fix Commit(s) -

O3 Security · Impact-Aware SCA

Is GHSA-q3jj-46pq-826r in your dependencies?

O3 detects GHSA-q3jj-46pq-826r 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