How severe is GHSA-q447-rj3r-2cgh?

GHSA-q447-rj3r-2cgh has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-q447-rj3r-2cgh?

GHSA-q447-rj3r-2cgh affects the following packages: openclaw (npm), clawdbot (npm). Ecosystems affected: npm.

How do I fix GHSA-q447-rj3r-2cgh?

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

How do I detect GHSA-q447-rj3r-2cgh 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-q447-rj3r-2cgh 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-q447-rj3r-2cgh?

O3 pinpoints whether GHSA-q447-rj3r-2cgh 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-q447-rj3r-2cgh actively exploited in the wild?

No public exploit code has been indexed for GHSA-q447-rj3r-2cgh 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-q447-rj3r-2cgh?

GHSA-q447-rj3r-2cgh has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th 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-q447-rj3r-2cgh?

GHSA-q447-rj3r-2cgh is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-q447-rj3r-2cgh published, and has it been updated?

GHSA-q447-rj3r-2cgh was published on February 18, 2026 and was last updated on March 5, 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-q447-rj3r-2cgh

HIGH

OpenClaw affected by denial of service via unbounded webhook request body buffering

Also known asCVE-2026-28478

Published

Feb 18, 2026

Updated

Mar 5, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk35th percentile+0.29%

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

2 pkgs affected

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

openclawnpm

4.4Mdownloads / week

clawdbotnpm

10Kdownloads / week

Description

Summary

Multiple webhook handlers accepted and buffered request bodies without a strict unified byte/time limit. A remote unauthenticated attacker could send oversized payloads and cause memory pressure, degrading availability.

Details

Affected packages:

openclaw (npm): <2026.2.12
clawdbot (npm): <=2026.1.24-3

Root cause:

Webhook code paths buffered request payloads without consistent maxBytes + timeoutMs enforcement.
Some SDK-backed handlers parse request bodies internally and needed stream-level guards.

Attack shape:

Send very large JSON payloads or slow/incomplete uploads to webhook endpoints.
Observe elevated memory usage and request handler pressure.

Impact

Remote unauthenticated availability impact (DoS) via request body amplification/memory pressure.

Patch details (implemented)

Added shared bounded request-body helper in src/infra/http-body.ts.
Exported helper in src/plugin-sdk/index.ts for extension reuse.
Migrated webhook body readers to shared helper for:
- LINE
- Nextcloud Talk
- Google Chat
- Zalo
- BlueBubbles
- Nostr profile HTTP
- Voice-call
- Gateway hooks
Added stream guards for SDK handlers that parse request bodies internally:
- Slack
- Telegram
- Feishu
Added explicit Express JSON body limit handling for MS Teams webhook path.
Standardized failure responses:
- 413 Payload Too Large
- 408 Request Timeout

Tests

Added regression tests:
- src/infra/http-body.test.ts
- src/line/monitor.read-body.test.ts
- extensions/nextcloud-talk/src/monitor.read-body.test.ts
Focused webhook/security test suite passes for patched paths.

Remediation

Upgrade to the first release containing this patch.

Credits

Thanks @vincentkoc for reporting.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.13
📦npm	`clawdbot`	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.
Fix
Update openclaw to 2026.2.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q447-rj3r-2cgh 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-q447-rj3r-2cgh 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-q447-rj3r-2cgh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Multiple webhook handlers accepted and buffered request bodies without a strict unified byte/time limit. A remote unauthenticated attacker could send oversized payloads and cause memory pressure, degrading availability. ### Details Affected packages: - `openclaw` (npm): `<2026.2.12` - `clawdbot` (npm): `<=2026.1.24-3` Root cause: - Webhook code paths buffered request payloads without consistent `maxBytes` + `timeoutMs` enforcement. - Some SDK-backed handlers parse request bodies internally and needed stream-level guards. Attack shape: - Send very large JSON payloads or slow/inco

O3 Security · Impact-Aware SCA

Is GHSA-q447-rj3r-2cgh in your dependencies?

O3 detects GHSA-q447-rj3r-2cgh 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