Authentication bypass via stale reload closure
Published Apr 28, 2026 · Updated Apr 28, 2026
Authentication bypass in OpenClaw before 2026.4.8 allows remote authenticated users to retain outdated gateway access after a config reload. The Gateway connection path closes over resolvedAuth and fails to refresh that captured state when a validated configuration reload replaces the active authentication settings. Exploitation requires a successful reload, affects newly accepted connections, and remains within OpenClaw's user-controlled assistant trust model.
Summary
What happened
Authentication bypass in OpenClaw before 2026.4.8 allows remote authenticated users to retain outdated gateway access after a config reload. The Gateway connection path closes over resolvedAuth and fails to refresh that captured state when a validated configuration reload replaces the active authentication settings. Exploitation requires a successful reload, affects newly accepted connections, and remains within OpenClaw's user-controlled assistant trust model.
The record
- CVE
- CVE-2026-41916
- Published
- Apr 28, 2026
- Updated
- Apr 28, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-613, T1556
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 28, 2026CVE publishedPublication date reported by the CVE source.
- Apr 28, 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.8
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.
Weakness, pattern, technique
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