GHSA-gc9r-867r-j85f

GHSA-gc9r-867r-j85f LOW
Published April 17, 2026

## Summary Microsoft Teams SSO invoke handler missed sender authorization checks. ## Affected Packages / Versions - Package: `openclaw` - Ecosystem: npm - Affected versions: `>= 2026.4.10 < 2026.4.14` - Patched versions: `>= 2026.4.14` ## Impact Microsoft Teams SSO signin invoke handling could...

Full CISO analysis pending enrichment.

Affected Systems

Package Ecosystem Vulnerable Range Patched
openclaw npm >= 2026.4.10, < 2026.4.14 2026.4.14
2 dependents 92% patched ~1d to patch Full package profile →

Do you use openclaw? You're affected.

Severity & Risk

CVSS 3.1
N/A
EPSS
N/A
Exploitation Status
No known exploitation
Sophistication
N/A

Recommended Action

Patch available

Update openclaw to version 2026.4.14

Compliance Impact

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is GHSA-gc9r-867r-j85f?

OpenClaw: Microsoft Teams SSO invoke handler missed sender authorization checks

Is GHSA-gc9r-867r-j85f actively exploited?

No confirmed active exploitation of GHSA-gc9r-867r-j85f has been reported, but organizations should still patch proactively.

How to fix GHSA-gc9r-867r-j85f?

Update to patched version: openclaw 2026.4.14.

What is the CVSS score for GHSA-gc9r-867r-j85f?

No CVSS score has been assigned yet.

Technical Details

NVD Description

## Summary Microsoft Teams SSO invoke handler missed sender authorization checks. ## Affected Packages / Versions - Package: `openclaw` - Ecosystem: npm - Affected versions: `>= 2026.4.10 < 2026.4.14` - Patched versions: `>= 2026.4.14` ## Impact Microsoft Teams SSO signin invoke handling could process an invoke from a sender before applying the same sender allowlist checks used by normal message handling. ## Technical Details The fix routes SSO invoke handling through the Teams sender authorization path and adds coverage for denied senders. ## Fix The issue was fixed in #66033. The first stable tag containing the fix is `v2026.4.14`, and `openclaw@2026.4.14` includes the fix. ## Fix Commit(s) - `80b1fa17bfc3f6a668492f0326ea52f48bb89776` - PR: #66033 ## Release Process Note Users should upgrade to `openclaw` 2026.4.14 or newer. The latest npm release, `2026.4.14`, already includes the fix. ## Credits Thanks to @zsxsoft, with sponsorship from @KeenSecurityLab and @qclawer for reporting this issue.

Timeline

Published
April 17, 2026
Last Modified
April 17, 2026
First Seen
April 18, 2026

Related Vulnerabilities