GHSA-6RMX-GVVG-VH6J

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

Fix Commit(s)

• 44820dceadac65ac7c0ce8fc0ffba8c2bd9fae89

Verification

• pnpm check passed
• pnpm 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.

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.

GHSA-6RMX-GVVG-VH6J has a CVSS score of 5.3 (Medium). 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.3.7); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-6RMX-GVVG-VH6J? GHSA-6RMX-GVVG-VH6J is a medium-severity security vulnerability in openclaw (npm), affecting versions <= 2026.3.2. It is fixed in 2026.3.7.
2. How severe is GHSA-6RMX-GVVG-VH6J? GHSA-6RMX-GVVG-VH6J has a CVSS score of 5.3 (Medium). 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.
3. Which versions of openclaw are affected by GHSA-6RMX-GVVG-VH6J? openclaw (npm) versions <= 2026.3.2 is affected.
4. Is there a fix for GHSA-6RMX-GVVG-VH6J? Yes. GHSA-6RMX-GVVG-VH6J is fixed in 2026.3.7. Upgrade to this version or later.
5. Is GHSA-6RMX-GVVG-VH6J exploitable, and should I be worried? Whether GHSA-6RMX-GVVG-VH6J 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
6. What actually determines whether GHSA-6RMX-GVVG-VH6J 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.
7. How do I fix GHSA-6RMX-GVVG-VH6J? Upgrade openclaw to 2026.3.7 or later.