OpenClaw up to 2026.4.22 SecretRef operation after expiration
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OpenClaw up to 2026.4.22. It has been classified as problematic. This impacts an unknown function. Performing a manipulation of the argument SecretRef results in operation after expiration. This vulnerability is known as CVE-2026-45005. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic has been found in OpenClaw up to 2026.4.22. This affects an unknown code block. The manipulation of the argument SecretRef with an unknown input leads to a operation after expiration vulnerability. CWE is classifying the issue as CWE-672. The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
OpenClaw before 2026.4.23 caches resolved webhook route secrets backed by SecretRef values, allowing stale secrets to remain valid after rotation and reload. Attackers with previously valid webhook route secrets can continue authenticating requests and invoking configured webhook task flows until gateway or plugin restart.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-45005 since 05/08/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The exploitation requires an enhanced level of successful authentication. Technical details are known, but no exploit is available.
Upgrading to version 2026.4.23 eliminates this vulnerability. Applying the patch 36c4a372a0ad5dca8bfc0d93f7aab9c2f2de66fa is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 2026.4.0
- 2026.4.1
- 2026.4.2
- 2026.4.3
- 2026.4.4
- 2026.4.5
- 2026.4.6
- 2026.4.7
- 2026.4.8
- 2026.4.9
- 2026.4.10
- 2026.4.11
- 2026.4.12
- 2026.4.13
- 2026.4.14
- 2026.4.15
- 2026.4.16
- 2026.4.17
- 2026.4.18
- 2026.4.19
- 2026.4.20
- 2026.4.21
- 2026.4.22
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 4.7
VulDB Temp Score: 4.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.0
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Operation after expirationCWE: CWE-672
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: OpenClaw 2026.4.23
Patch: 36c4a372a0ad5dca8bfc0d93f7aab9c2f2de66fa
Timeline
05/08/2026 CVE reserved05/11/2026 Advisory disclosed
05/11/2026 VulDB entry created
05/11/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-q8ff-7ffm-m3r9
Status: Confirmed
CVE: CVE-2026-45005 (🔒)
GCVE (CVE): GCVE-0-2026-45005
GCVE (VulDB): GCVE-100-362745
Entry
Created: 05/11/2026 20:42Changes: 05/11/2026 20:42 (78)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.