How severe is GHSA-cxpw-2g23-2vgw?

No CVSS score has been assigned to GHSA-cxpw-2g23-2vgw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cxpw-2g23-2vgw?

GHSA-cxpw-2g23-2vgw affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix GHSA-cxpw-2g23-2vgw?

Update openclaw to 2026.2.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cxpw-2g23-2vgw is resolved across your whole dependency graph.

How do I detect GHSA-cxpw-2g23-2vgw 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-cxpw-2g23-2vgw 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-cxpw-2g23-2vgw?

O3 pinpoints whether GHSA-cxpw-2g23-2vgw 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-cxpw-2g23-2vgw actively exploited in the wild?

No public exploit code has been indexed for GHSA-cxpw-2g23-2vgw 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-cxpw-2g23-2vgw?

GHSA-cxpw-2g23-2vgw is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cxpw-2g23-2vgw published, and has it been updated?

GHSA-cxpw-2g23-2vgw was published on February 20, 2026 and was last updated on February 23, 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-cxpw-2g23-2vgw

Fix: openclaw/openclaw@63e39d7

GHSA-cxpw-2g23-2vgw is a Uncontrolled Resource Consumption vulnerability in openclaw. O3 Security confirms whether GHSA-cxpw-2g23-2vgw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw: ACP prompt-size checks missing in local stdio bridge could reduce responsiveness with very large inputs

Also known asCVE-2026-27576

Published

Feb 20, 2026

Updated

Feb 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 23, 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

Vulnerability

The ACP bridge accepted very large prompt text blocks and could assemble oversized prompt payloads before forwarding them to chat.send.

Because ACP runs over local stdio, this mainly affects local ACP clients (for example IDE integrations) that send unusually large inputs.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.2.17
Patched version: 2026.2.18 (planned next release)

Impact

Local ACP sessions may become less responsive when very large prompts are submitted
Larger-than-expected model usage/cost when oversized text is forwarded
No privilege escalation and no direct remote attack path in the default ACP model

Affected Components

src/acp/event-mapper.ts
src/acp/translator.ts

Remediation

Enforce a 2 MiB prompt-text limit before concatenation
Count inter-block newline separator bytes during pre-concatenation size checks
Keep final outbound message-size validation before chat.send
Avoid stale active-run session state when oversized prompts are rejected
Add regression tests for oversize rejection and active-run cleanup

Fix Commit(s)

732e53151e8fbdfc0501182ddb0e900878bdc1e3
ebcf19746f5c500a41817e03abecadea8655654a
63e39d7f57ac4ad4a5e38d17e7394ae7c4dd0b9c

Thanks @aether-ai-agent for reporting.

Affected Packages

1 total 1 fixed

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

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

Frequently Asked Questions

## Vulnerability The ACP bridge accepted very large prompt text blocks and could assemble oversized prompt payloads before forwarding them to `chat.send`. Because ACP runs over local stdio, this mainly affects local ACP clients (for example IDE integrations) that send unusually large inputs. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `<= 2026.2.17` - Patched version: `2026.2.18` (planned next release) ## Impact - Local ACP sessions may become less responsive when very large prompts are submitted - Larger-than-expected model usage/cost when oversized

O3 Security · Impact-Aware SCA

Is GHSA-cxpw-2g23-2vgw in your dependencies?

O3 detects GHSA-cxpw-2g23-2vgw 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