OpenClaw MS Teams before 2026.5.12 contain an authorization bypass vulnerability where the allowFrom feature binds to mutable display names. Attackers with lower-trust access can perform actions requiring stronger authorization by exploiting the mutable display name binding in the affected feature.
CVE-2026-62224
Score 5.4 from GitHub Security Advisory (severity: LOW) published 2026-07-17. a secondary CVSS source baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EG Risk
- 24(Track)EG Risk 24/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 5.1%
- KEV
- Not listed
Published
July 17, 2026
Last Modified
July 17, 2026
Advisory Details (2)
Auto-updated Jul 17, 2026OpenClaw MS Teams < 2026.5.12 Authorization Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/openclaw-ms-teams-authorization-bypass[AgentGG] MS Teams allowFrom could bind to mutable display names · Advisory · openclaw/openclaw · GitHub
https://github.com/openclaw/openclaw/security/advisories/GHSA-7w4v-g4m6-j88vVendor Advisories for CVE-2026-62224(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× 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.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:21 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-18 20:29 UTCEG score recompute
- 2026-07-18 20:29 UTCGHSA enrichment
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 14:51 UTCEG score recompute
- 2026-07-17 14:51 UTCGHSA enrichment
- 2026-07-17 06:54 UTCGHSA enrichment
- 2026-07-17 00:26 UTCEG score recompute
- 2026-07-17 00:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-62224?
When was CVE-2026-62224 disclosed?
Is CVE-2026-62224 actively exploited?
What is the CVSS score of CVE-2026-62224?
How do I remediate CVE-2026-62224?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-62224
Is Your Infrastructure Affected by CVE-2026-62224?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.