Authorization Bypass in OpenClaw: Microsoft Teams SSO Handler Vulnerability

openclaw Updated 18 Apr 2026

Summary

17/04/2026

Disclosed on

LOW

Severity

Yes i

Fix available

Low

Severity

1.7

CVSS Score

GHSA-gc9r-867r-j85f: OpenClaw: Microsoft Teams SSO invoke handler missed sender authorization checks. Affects openclaw versions >= 2026.4.10, < 2026.4.14. Fixed in 2026.4.14. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

OpenClaw is an npm package designed to facilitate integration with Microsoft Teams, providing functionalities such as Single Sign-On (SSO) capabilities. It allows applications to authenticate users seamlessly within the Teams environment. However, a recent vulnerability was identified in its SSO invoke handler, which failed to implement necessary sender authorization checks, potentially allowing unauthorized access.

Vulnerability Detail

The vulnerability arises from the Microsoft Teams SSO invoke handler's failure to enforce sender authorization checks. This oversight means that an invoke from an unauthorized sender could be processed without the usual checks, leading to potential unauthorized access to sensitive functionalities. The issue was identified in versions of OpenClaw from 2026.4.10 to 2026.4.13, and it was addressed by routing SSO invoke handling through the proper authorization path, ensuring that denied senders are appropriately handled.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.4.14

This is the first release that contains the fix.

npm install openclaw@2026.4.14

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. The best course of action is to upgrade to the patched version as soon as possible.

Conclusion

In summary, the OpenClaw package has a vulnerability in its Microsoft Teams SSO invoke handler that could allow unauthorized access due to missed sender authorization checks. Users are strongly advised to upgrade to version 2026.4.14 or newer to mitigate this risk.

See every vulnerability recorded for openclaw →