Cyber Resilience

CVE-2026-28481

Info Disclosure in Openclaw ≤ 2026.1.30

Public PoCInfo Disclosure
Published
05 March 2026
Modified
17 March 2026
Patch / advisory
CVSS Score v4 5.9
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0026 18th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-28481 is a medium-severity Insertion of Sensitive Information Into Sent Data (CWE-201) vulnerability in Openclaw Openclaw. Its CVSS base score is 5.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-28481 is an information disclosure vulnerability (CWE-201) affecting OpenClaw versions 2026.1.30 and earlier, with a CVSS v3.1 base score of 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N). The issue resides in the optional MS Teams attachment downloader extension, which must be explicitly enabled. When the downloader retries failed attachment fetches after receiving HTTP 401 or 403 responses, it erroneously sends Authorization bearer tokens to untrusted hosts that match a permissive suffix-based allowlist, enabling potential token exfiltration.

Attackers can exploit this vulnerability remotely without privileges by tricking a user into attempting to download an MS Teams attachment from a malicious domain that matches the application's suffix allowlist. User interaction is required, such as clicking a link or triggering the downloader. Successful exploitation allows the attacker to capture the leaked bearer tokens, which could grant unauthorized access to the victim's MS Teams resources or associated services depending on the token's scope.

The vulnerability has been patched in OpenClaw version 2026.2.1, as detailed in the project's GitHub commit (41cc5bcd4f1d434ad1bbdfa55b56f25025ecbf6b), security advisory (GHSA-7vwx-582j-j332), and VulnCheck analysis. Security practitioners should advise users to update to the fixed version immediately and consider disabling the MS Teams attachment downloader extension if not needed, pending patch deployment.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

responses, the application sends Authorization bearer tokens to untrusted hosts matching the permissive suffix-based allowlist, enabling token theft.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1040 Network Sniffing Credential Access
Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-28479Same product: Openclaw Openclaw
CVE-2026-40045Same product: Openclaw Openclaw
CVE-2026-32065Same product: Openclaw Openclaw
CVE-2026-8305Same product: Openclaw Openclaw
CVE-2026-28471Same product: Openclaw Openclaw
CVE-2026-35643Same product: Openclaw Openclaw
CVE-2026-32987Same product: Openclaw Openclaw
CVE-2026-32053Same product: Openclaw Openclaw
CVE-2026-28449Same product: Openclaw Openclaw
CVE-2026-41351Same product: Openclaw Openclaw

Affected Assets

openclaw
openclaw
≤ 2026.1.30

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V14.2.3

Mitigating Controls (NIST 800-53 r5) AI

Directly enforces policy-based information flow rules that block transmission of sensitive data to unauthorized actors.

Enforces authorizations on logical access so that sensitive data is not released to unauthorized recipients.

Requires validation of outbound information to ensure sensitive content is not disclosed in responses or messages.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent insertion of sensitive data into application outputs and messages.

DE.CM-09 partial match
prevents

Monitoring runtime data flows and outputs can detect sensitive data being transmitted.

PR.DS-02 partial match
prevents

Protecting data-in-transit can include filtering or encrypting to avoid exposing sensitive content.

PR.DS-10 partial match
prevents

Protecting data-in-use includes removing confidential values before they are processed or sent.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Data-masking techniques can prevent sensitive values from appearing in transmitted payloads.

mitigates

Classification identifies sensitive data so it is not inadvertently transmitted.

mitigates

Labelling makes sensitive data visible to developers and prevents accidental inclusion in outbound messages.

mitigates

Information-transfer rules directly govern what data may be sent to external parties.

mitigates

PII-protection requirements reduce the chance of sending personal data to unauthorized recipients.

mitigates

DLP controls inspect and block outbound flows that contain sensitive information.

References