OpenClaw MS Teams inbound attachment downloader leaks bearer tokens to allowlisted suffix domains
CVE-2026-28481GHSA-7vwx-582j-j332
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (openclaw 2026.2.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm openclaw
- Affected
- < 2026.2.1
- Fixed in
- 2026.2.1
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-7vwx-582j-j332 lists affected ranges: npm openclaw >=0 <2026.2.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-7vwx-582j-j332 lists affected ranges: npm openclaw >=0 <2026.2.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 5.9 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2026-28481: 0.30% estimated exploitation activity in the next 30 days; percentile 23.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary NOTE: This only affects deployments that enable the optional MS Teams extension (Teams channel). If you do not use MS Teams, you are not impacted. When OpenClaw downloads inbound MS Teams attachments / inline images, it may retry a URL with an Authorization: Bearer <token header after receiving 401 or 403. Because the default download allowlist uses suffix matching (and includes some multi-tenant suffix domains), a message that references an untrusted but allowlisted host could cause that bearer token to be sent to the wrong place. Affected Packages / Versions - Package: openclaw (npm) - Vulnerable: <= 2026.1.30 - Patched: = 2026.2.1 Fix - Fix commit: 41cc5bcd4f1d434ad1bbdfa55b56f25025ecbf6b - Upgrade to openclaw = 2026.2.1 Workarounds - If you do not need MS Teams, disable the MS Teams extension. - If you must stay on an older version, ensure the auth host allowlist is strict (only Microsoft-owned endpoints that require auth) and avoid wildcard or broad suffix entries.…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-7vwx-582j-j332
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-7vwx-582j-j332
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-28481 Advisory: OpenClaw MS Teams inbound attachment downloader leaks bearer tokens to allowlisted suffix domains IDs: CVE-2026-28481, GHSA-7vwx-582j-j332 Record: https://patchnext.com/advisories/cve-2026-28481 (revision 3, source checked 26 Oct 2026, 12:43 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: openclaw 2026.2.1. A vendor fix does not mean a deployment is fixed. ## Affected components - npm openclaw: affected < 2026.2.1; fixed in 2026.2.1 ## Suggested inspection (read-only) - `npm ls openclaw --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on openclaw. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-7vwx-582j-j332 (OSV record GHSA-7vwx-582j-j332 lists affected ranges: npm openclaw >=0 <2026.2.1 (fixed)) - Verified: https://github.com/advisories/GHSA-7vwx-582j-j332 (GitHub-reviewed advisory GHSA-7vwx-582j-j332 lists affected ranges: npm openclaw >=0 <2026.2.1) Commands are suggestions: review each one before running it.
Loading voting…