OpenClaw up to 2026.1.30 Bearer Token insertion of sensitive information into sent data
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in OpenClaw up to 2026.1.30. This vulnerability affects unknown code of the component Bearer Token Handler. The manipulation leads to insertion of sensitive information into sent data. This vulnerability is referenced as CVE-2026-28481. Remote exploitation of the attack is possible. No exploit is available. It is suggested to install a patch to address this issue.
Details
A vulnerability was found in OpenClaw up to 2026.1.30 and classified as problematic. This issue affects an unknown functionality of the component Bearer Token Handler. The manipulation with an unknown input leads to a insertion of sensitive information into sent data vulnerability. Using CWE to declare the problem leads to CWE-201. The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. Impacted is confidentiality. The summary by CVE is:
OpenClaw versions 2026.1.30 and earlier, contain an information disclosure vulnerability, patched in 2026.2.1, in the MS Teams attachment downloader (optional extension must be enabled) that leaks bearer tokens to allowlisted suffix domains. When retrying downloads after receiving 401 or 403 responses, the application sends Authorization bearer tokens to untrusted hosts matching the permissive suffix-based allowlist, enabling token theft.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-28481 since 02/27/2026. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Applying the patch 41cc5bcd4f1d434ad1bbdfa55b56f25025ecbf6b is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 2026.1.0
- 2026.1.1
- 2026.1.2
- 2026.1.3
- 2026.1.4
- 2026.1.5
- 2026.1.6
- 2026.1.7
- 2026.1.8
- 2026.1.9
- 2026.1.10
- 2026.1.11
- 2026.1.12
- 2026.1.13
- 2026.1.14
- 2026.1.15
- 2026.1.16
- 2026.1.17
- 2026.1.18
- 2026.1.19
- 2026.1.20
- 2026.1.21
- 2026.1.22
- 2026.1.23
- 2026.1.24
- 2026.1.25
- 2026.1.26
- 2026.1.27
- 2026.1.28
- 2026.1.29
- 2026.1.30
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.7VulDB Meta Temp Score: 5.7
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔒
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: Insertion of sensitive information into sent dataCWE: CWE-201 / 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: PatchStatus: 🔍
0-Day Time: 🔒
Patch: 41cc5bcd4f1d434ad1bbdfa55b56f25025ecbf6b
Timeline
02/27/2026 CVE reserved03/06/2026 Advisory disclosed
03/06/2026 VulDB entry created
03/17/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-7vwx-582j-j332
Status: Confirmed
CVE: CVE-2026-28481 (🔒)
GCVE (CVE): GCVE-0-2026-28481
GCVE (VulDB): GCVE-100-349385
Entry
Created: 03/06/2026 07:47Updated: 03/17/2026 20:06
Changes: 03/06/2026 07:47 (76), 03/08/2026 04:26 (4), 03/10/2026 14:54 (1), 03/17/2026 20:06 (12)
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.