OpenClaw: MS Teams webhook parses body before JWT validation, enabling unauthenticated resource exhaustionGHSA-p464-m8x6-vhv8
HIGHFix: openclaw/openclaw@3834d47GHSA-p464-m8x6-vhv8 is a high-severity (CVSS 7.5) CWE-408 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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.
openclawnpmDescription
Summary
MS Teams webhook parses body before JWT validation, enabling unauthenticated resource exhaustion
Current Maintainer Triage
- Status: open
- Normalized severity: medium
- Assessment: v2026.3.28 still parses Teams JSON after only a Bearer-prefix gate and before real JWT validation, and the auth-before-parse fix is not yet shipped.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published npm version:
2026.3.31 - Vulnerable version range:
<=2026.3.28 - Patched versions:
>= 2026.3.31 - First stable tag containing the fix:
v2026.3.31
Fix Commit(s)
3834d47099dd13c8244ed6de8b9ea9855c553623— 2026-03-30T13:46:40+01:00
OpenClaw thanks @AntAISecurityLab for reporting.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.3.31npm install openclaw@2026.3.31 |
Affected Products
openclawopenclawDetection & 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.3.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p464-m8x6-vhv8 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-p464-m8x6-vhv8 in your dependencies?
Find it across npm, including transitive dependencies.