OpenClaw: MS Teams Feedback Invocation Bypasses Sender Allowlists and Records Unauthorized Session Feedback

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2026-35654: 0.23% estimated exploitation activity in the next 30 days; percentile 13.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary MS Teams Feedback Invoke Bypasses Sender Allowlists and Records Unauthorized Session Feedback Affected Packages / Versions - Package: openclaw - Affected versions: <= 2026.3.24 - First patched version: 2026.3.25 - Latest published npm version at verification time: 2026.3.24 Details Microsoft Teams feedback invokes previously bypassed sender authorization and could record feedback or trigger reflection for unauthorized senders. Commit c5415a474bb085404c20f8b312e436997977b1ea applies the same DM and group authorization checks to feedback invokes. Verified vulnerable on tag v2026.3.24 and fixed on main by commit c5415a474bb085404c20f8b312e436997977b1ea. Fix Commit(s) - c5415a474bb085404c20f8b312e436997977b1ea

Published by the source

29 Mar 2026, 15:49 UTC

Last modified by the source

10 Apr 2026, 17:42 UTC

Source last checked

26 Oct 2026, 12:48 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rf6h-5gpw-qrgq

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-rf6h-5gpw-qrgq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-35654

Advisory: OpenClaw: MS Teams Feedback Invocation Bypasses Sender Allowlists and Records Unauthorized Session Feedback
IDs: CVE-2026-35654, GHSA-rf6h-5gpw-qrgq
Record: https://patchnext.com/advisories/cve-2026-35654 (revision 2, source checked 26 Oct 2026, 12:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openclaw 2026.3.28. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm openclaw: affected <= 2026.3.24; fixed in 2026.3.28

## 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-rf6h-5gpw-qrgq (OSV record GHSA-rf6h-5gpw-qrgq lists affected ranges: npm openclaw >=0 <2026.3.28 (fixed))
- Verified: https://github.com/advisories/GHSA-rf6h-5gpw-qrgq (GitHub-reviewed advisory GHSA-rf6h-5gpw-qrgq lists affected ranges: npm openclaw >=0 <=2026.3.24)

Commands are suggestions: review each one before running it.