CVE-2026-33578

OpenClaw · Vulnerability

CVSS 4.0 5.3 MEDIUMCVSS 3.1 4.3 MEDIUMEUVD CVSS 4.0 5.3 CVSS 4.0 · [email protected] · Secondary 5.3 MEDIUMCVSS 3.1 · [email protected] · Secondary 4.3 MEDIUMCVSS 3.1 · [email protected] · Primary 4.3 MEDIUMCVSS_V3 CVSS_V4 Publisher rating MODERATEFixed by openclaw 2026.3.28KEV status unknown

Original advisory

cve-program · CVE-2026-33578

Published

OpenClaw before 2026.3.28 contains a sender policy bypass vulnerability in the Google Chat and Zalouser extensions where route-level group allowlist policies silently downgrade to open policy. Attackers can exploit this policy resolution flaw to bypass sender restrictions and interact with bots despite configured allowlist restrictions.

Read the publisher's advisory

euvd · EUVD-2026-17435

Published

Read the publisher's advisory

nvd · CVE-2026-33578

Published

Read the publisher's advisory

osv · GHSA-63mg-xp9j-jfcm

Published

## Summary When only a route-level group allowlist was configured, sender policy resolution silently downgraded from `allowlist` to `open` instead of preserving the configured group policy. ## Impact Any member of an allowlisted Google Chat space or Zalouser group could interact with the bot even when the operator intended sender-level restrictions. ## Affected Component `extensions/googlechat/src/monitor-access.ts, extensions/zalouser/src/monitor.ts` ## Fixed Versions - Affected: `<= 2026.3.24` - Patched: `>= 2026.3.28` - Latest stable `2026.3.28` contains the fix. ## Fix Fixed by commit `e64a881ae0` (`Channels: preserve routed group policy`). OpenClaw thanks @AntAISecurityLab for reporting.

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and daily EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Other daily score changes remain in this history.

Advisory history

11 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

11 Nov 2026 08:38:03 UTC