Skip to main content
CVE-2026-34506VulnerabilityPublished Updated

Openclaw cli: OpenClaw's MS Teams sender allowlist bypass when route allowlist is configured and sender allowlist is

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 2026.3.8 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.8
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.8.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.3.8
Fixed in
  • 2026.3.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in OpenClaw CLI version 2026.3.8. Users should upgrade to this version or later to remediate the vulnerability. No additional mitigation steps are required beyond applying the official fix.

Description

OpenClaw's Microsoft Teams plugin had a vulnerability where configuring a route allowlist without any sender allowlist entries allowed unauthorized senders within matched Teams routes to bypass sender authorization checks. This issue was fixed in version 2026.3.8.

References

Community reviews

Loading reviews…