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.
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.
Credits
Thanks @vincentkoc for reporting.
Impact
Remote unauthenticated availability impact (DoS) via request body amplification/memory pressure.
Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.
CVE-2026-28478 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.13); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Upgrade to the first release containing this patch.
Frequently Asked Questions
- What is CVE-2026-28478? CVE-2026-28478 is a high-severity uncontrolled resource consumption vulnerability in openclaw (npm), affecting versions < 2026.2.13. It is fixed in 2026.2.13. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
- How severe is CVE-2026-28478? CVE-2026-28478 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2026-28478?
openclaw(npm) (versions < 2026.2.13)clawdbot(npm) (versions <= 2026.1.24-3)
- Is there a fix for CVE-2026-28478? Yes. CVE-2026-28478 is fixed in 2026.2.13. Upgrade to this version or later.
- Is CVE-2026-28478 exploitable, and should I be worried? Whether CVE-2026-28478 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-28478 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-28478? Upgrade
openclawto 2026.2.13 or later.