CVE-2026-32924

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory published 2026-03-29. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, ghsa
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

OpenClaw before 2026.3.12 contains an authorization bypass vulnerability where Feishu reaction events with omitted chat_type are misclassified as p2p conversations instead of group chats. Attackers can exploit this misclassification to bypass groupAllowFrom and requireMention protections in group chat reaction-derived events.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
22.8%
KEV
Not listed

Published

March 29, 2026

Last Modified

June 23, 2026

Advisory Details (2)

Auto-updated Jul 12, 2026
Patch available. Sources: github.
generic

OpenClaw < 2026.3.12 - Authorization Bypass via Misclassified Reaction Events in Feishu | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-authorization-bypass-via-misclassified-reaction-events-in-feishu
github Patch Available

Feishu reaction events could bypass group authorization and mention gating · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-m69h-jm2f-2pv8

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 22:30 UTCEPSS rescore
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-08 15:15 UTCEPSS rescore
  8. 2026-07-07 13:46 UTCEPSS rescore
  9. 2026-07-06 16:27 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-06 02:23 UTCEPSS rescore
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-01 15:06 UTCEPSS rescore
  16. 2026-06-30 23:22 UTCEPSS rescore
  17. 2026-06-29 14:06 UTCEPSS rescore
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-27 03:19 UTCEG score recompute
  24. 2026-06-27 03:19 UTCGHSA enrichment
  25. 2026-06-27 03:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-32924?
CVE-2026-32924 is a critical vulnerability published on March 29, 2026. OpenClaw before 2026.3.12 contains an authorization bypass vulnerability where Feishu reaction events with omitted chat_type are misclassified as p2p conversations instead of group chats. Attackers can exploit this misclassification to bypass groupAllowFrom and requireMention protections in group…
When was CVE-2026-32924 disclosed?
CVE-2026-32924 was first published in the National Vulnerability Database on March 29, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32924 actively exploited?
CVE-2026-32924 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-32924?
CVE-2026-32924 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-32924?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32924, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-32924

Explore →

Is Your Infrastructure Affected by CVE-2026-32924?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs