Webhook routing bypass via templated session keys
Published May 11, 2026 · Updated May 11, 2026
Incorrect authorization in OpenClaw before 2026.4.20 allows remote attackers to alter webhook session routing through hook mappings. The Gateway treats template-rendered mapping session keys differently from request-supplied keys, allowing externally influenced values despite a disabled hooks.allowRequestSessionKey setting. Exploitation requires a configured templated hook mapping; the bypass breaks routing isolation but does not itself grant host execution.
Summary
What happened
Incorrect authorization in OpenClaw before 2026.4.20 allows remote attackers to alter webhook session routing through hook mappings. The Gateway treats template-rendered mapping session keys differently from request-supplied keys, allowing externally influenced values despite a disabled hooks.allowRequestSessionKey setting. Exploitation requires a configured templated hook mapping; the bypass breaks routing isolation but does not itself grant host execution.
The record
- CVE
- CVE-2026-45002
- Published
- May 11, 2026
- Updated
- May 11, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 2026CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.4.20
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo