OpenClaw's hooks HTTP handler counted hook authentication failures before rejecting unsupported HTTP methods. An unauthenticated client could send repeated non-POST requests (for example GET) with an invalid token to consume the hook auth failure budget and trigger the temporary lockout window for that client key.
The fix moves the hook method gate ahead of auth-failure accounting so unsupported methods return 405 Method Not Allowed without incrementing the hook auth limiter.
Affected Packages / Versions
- Package:
openclaw (npm)
- Affected versions:
<= 2026.3.2
- Patched version:
2026.3.7
- Latest published npm version at patch time:
2026.3.2
Impact
An unauthenticated network client that could reach /hooks/* could temporarily lock out legitimate webhook delivery when requests collapsed to the same hook auth client key, such as shared proxy or NAT topologies. Impact is limited to temporary availability loss for hook-triggered wake or automation delivery.
Fix Commit(s)
44820dceadac65ac7c0ce8fc0ffba8c2bd9fae89
Verification
pnpm check passedpnpm test:fast passed- focused hook regression tests passed
pnpm exec vitest run --config vitest.gateway.config.ts still has unrelated current-main failures in src/gateway/server-channels.test.ts and src/gateway/server-methods/agents-mutate.test.ts
Release Process Note
npm 2026.3.7 was published on March 8, 2026. This advisory is fixed in the released package.
Thanks @JNX03 for reporting.
References
JNX03 Reporter
OpenClaw's hooks HTTP handler counted hook authentication failures before rejecting unsupported HTTP methods. An unauthenticated client could send repeated non-
POSTrequests (for exampleGET) with an invalid token to consume the hook auth failure budget and trigger the temporary lockout window for that client key.The fix moves the hook method gate ahead of auth-failure accounting so unsupported methods return
405 Method Not Allowedwithout incrementing the hook auth limiter.Affected Packages / Versions
openclaw(npm)<= 2026.3.22026.3.72026.3.2Impact
An unauthenticated network client that could reach
/hooks/*could temporarily lock out legitimate webhook delivery when requests collapsed to the same hook auth client key, such as shared proxy or NAT topologies. Impact is limited to temporary availability loss for hook-triggered wake or automation delivery.Fix Commit(s)
44820dceadac65ac7c0ce8fc0ffba8c2bd9fae89Verification
pnpm checkpassedpnpm test:fastpassedpnpm exec vitest run --config vitest.gateway.config.tsstill has unrelated current-mainfailures insrc/gateway/server-channels.test.tsandsrc/gateway/server-methods/agents-mutate.test.tsRelease Process Note
npm
2026.3.7was published on March 8, 2026. This advisory is fixed in the released package.Thanks @JNX03 for reporting.
References