OpenClaw up to 2026.4.13 removal of sensitive information
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.86 |
Summary
A vulnerability was found in OpenClaw up to 2026.4.13. It has been classified as problematic. This affects an unknown function. Performing a manipulation results in removal of sensitive information. This vulnerability is cataloged as CVE-2026-43528. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in OpenClaw up to 2026.4.13. It has been classified as problematic. This affects an unknown code block. The manipulation with an unknown input leads to a removal of sensitive information vulnerability. CWE is classifying the issue as CWE-212. The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors. This is going to have an impact on confidentiality. The summary by CVE is:
OpenClaw before 2026.4.14 contains a redaction bypass vulnerability that allows authenticated gateway clients to receive unredacted secrets through sourceConfig and runtimeConfig alias fields. Attackers with config read access can exploit this to obtain provider API keys, gateway authentication material, and channel credentials that should have been redacted.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-43528 since 05/01/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 2026.4.14 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1161). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Open Source OpenClaw
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
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.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
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: Removal of sensitive informationCWE: CWE-212 / CWE-200 / CWE-284
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.14
Timeline
05/01/2026 CVE reserved05/05/2026 Advisory disclosed
05/05/2026 VulDB entry created
05/06/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-43528 (🔒)
GCVE (CVE): GCVE-0-2026-43528
GCVE (VulDB): GCVE-100-361149
CERT Bund: WID-SEC-2026-1161 - OpenClaw: Mehrere Schwachstellen
Entry
Created: 05/05/2026 14:04Updated: 05/06/2026 10:32
Changes: 05/05/2026 14:04 (74), 05/06/2026 10:32 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.