CVE-2026-62213

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-07-17. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

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

OpenClaw versions before 2026.5.27 contain a token leakage vulnerability in MS Teams outbound requests that allows lower-trust callers to expose Bot Framework tokens. Attackers can access configured input paths to retrieve credentials that should remain within the trusted boundary.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/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 computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

July 17, 2026

Last Modified

July 21, 2026

Advisory Details (2)

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

OpenClaw < 2026.5.27 Token Leakage via MS Teams Outbound Requests | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-token-leakage-via-ms-teams-outbound-requests
github Patch Available

MS Teams outbound requests could leak Bot Framework tokens · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-v54h-q2vx-vgg4

Vendor Advisories for CVE-2026-62213(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 32× 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-28 17:08 UTCEG score recompute
  2. 2026-07-28 17:08 UTCGHSA enrichment
  3. 2026-07-28 15:37 UTCEPSS rescore
  4. 2026-07-27 14:14 UTCEPSS rescore
  5. 2026-07-27 13:33 UTCEG score recompute
  6. 2026-07-27 13:33 UTCGHSA enrichment
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 11:22 UTCEG score recompute
  10. 2026-07-26 11:22 UTCGHSA enrichment
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-25 14:18 UTCEPSS rescore
  13. 2026-07-24 14:18 UTCEPSS rescore
  14. 2026-07-24 14:18 UTCEPSS rescore
  15. 2026-07-23 14:18 UTCEPSS rescore
  16. 2026-07-23 14:18 UTCEPSS rescore
  17. 2026-07-23 03:21 UTCEG score recompute
  18. 2026-07-23 00:21 UTCEG score recompute
  19. 2026-07-23 00:21 UTCGHSA enrichment
  20. 2026-07-22 14:08 UTCEPSS rescore
  21. 2026-07-22 14:08 UTCEPSS rescore
  22. 2026-07-21 15:25 UTCEPSS rescore
  23. 2026-07-21 15:25 UTCEPSS rescore
  24. 2026-07-20 17:08 UTCEPSS rescore
  25. 2026-07-19 14:31 UTCEPSS rescore
Show 7 more
  1. 2026-07-19 02:29 UTCEPSS rescore
  2. 2026-07-18 23:25 UTCEG score recompute
  3. 2026-07-18 23:25 UTCGHSA enrichment
  4. 2026-07-18 10:04 UTCEPSS rescore
  5. 2026-07-17 06:55 UTCGHSA enrichment
  6. 2026-07-17 00:26 UTCEG score recompute
  7. 2026-07-17 00:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62213?
CVE-2026-62213 is a medium vulnerability published on July 17, 2026. OpenClaw versions before 2026.5.27 contain a token leakage vulnerability in MS Teams outbound requests that allows lower-trust callers to expose Bot Framework tokens. Attackers can access configured input paths to retrieve credentials that should remain within the trusted boundary.
When was CVE-2026-62213 disclosed?
CVE-2026-62213 was first published in the National Vulnerability Database on July 17, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62213 actively exploited?
CVE-2026-62213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.6% of all scored CVEs.
What is the CVSS score of CVE-2026-62213?
CVE-2026-62213 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-62213?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62213, 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-62213

Explore →

Is Your Infrastructure Affected by CVE-2026-62213?

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

Start Free Scan →Browse All CVEs