GHSA-q447-rj3r-2cgh — openclaw
HIGHGHSA-q447-rj3r-2cgh is a high-severity (CVSS 7.5) CWE-770 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.
OpenClaw affected by denial of service via unbounded webhook request body buffering
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-q447-rj3r-2cgh.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-q447-rj3r-2cgh plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
openclawnpmclawdbotnpmDescription
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.12clawdbot(npm):<=2026.1.24-3
Root cause:
- Webhook code paths buffered request payloads without consistent
maxBytes+timeoutMsenforcement. - 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.tsfor 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 Large408 Request Timeout
Tests
- Added regression tests:
src/infra/http-body.test.tssrc/line/monitor.read-body.test.tsextensions/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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.2.13npm install openclaw@2026.2.13 |
| 📦npm | clawdbot | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-q447-rj3r-2cgh can be triaged on real exposure rather than presence alone.
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
Is GHSA-q447-rj3r-2cgh in your dependencies?
O3 Security finds GHSA-q447-rj3r-2cgh across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.