CVE-2026-62195

HIGHPre-NVD 8.38.3—
EchelonGraph scoreHIGH confidence

Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. a secondary CVSS source baseline 8.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: None knownExposed: 0

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

OpenClaw versions 2026.5.20 before 2026.6.6 contain an authorization bypass vulnerability in the MCP loopback feature that allows lower-trust callers to execute owner-only tools. Attackers can bypass authorization checks through configured input paths to execute or persist actions beyond their intended permissions.

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

Published

July 13, 2026

Last Modified

July 15, 2026

Advisory Details (2)

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

OpenClaw 2026.5.20 < 2026.6.6 Authorization Bypass via MCP loopback | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-authorization-bypass-via-mcp-loopback
github Patch Available

MCP loopback could expose owner-only tools to non-owner runs · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-52xj-c9p8-78cv

Vendor Advisories for CVE-2026-62195(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 23× in last 7d / 41× 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-29 00:07 UTCEG score recompute
  2. 2026-07-29 00:07 UTCGHSA enrichment
  3. 2026-07-28 15:37 UTCEPSS rescore
  4. 2026-07-28 12:16 UTCGHSA enrichment
  5. 2026-07-28 00:26 UTCEG score recompute
  6. 2026-07-28 00:26 UTCGHSA enrichment
  7. 2026-07-27 14:14 UTCEPSS rescore
  8. 2026-07-27 11:34 UTCGHSA enrichment
  9. 2026-07-26 23:43 UTCEG score recompute
  10. 2026-07-26 23:43 UTCGHSA enrichment
  11. 2026-07-26 14:54 UTCEPSS rescore
  12. 2026-07-26 14:54 UTCEPSS rescore
  13. 2026-07-26 11:51 UTCEG score recompute
  14. 2026-07-26 11:51 UTCGHSA enrichment
  15. 2026-07-25 14:18 UTCEPSS rescore
  16. 2026-07-25 14:18 UTCEPSS rescore
  17. 2026-07-24 14:18 UTCEPSS rescore
  18. 2026-07-24 14:18 UTCEPSS rescore
  19. 2026-07-23 14:18 UTCEPSS rescore
  20. 2026-07-23 14:18 UTCEPSS rescore
  21. 2026-07-23 03:21 UTCEG score recompute
  22. 2026-07-22 14:08 UTCEPSS rescore
  23. 2026-07-22 14:08 UTCEPSS rescore
  24. 2026-07-21 15:25 UTCEPSS rescore
  25. 2026-07-21 15:25 UTCEPSS rescore
Show 16 more
  1. 2026-07-20 17:08 UTCEPSS rescore
  2. 2026-07-19 14:31 UTCEPSS rescore
  3. 2026-07-19 02:29 UTCEPSS rescore
  4. 2026-07-18 10:04 UTCEPSS rescore
  5. 2026-07-16 20:45 UTCGHSA enrichment
  6. 2026-07-16 17:03 UTCEPSS rescore
  7. 2026-07-16 08:55 UTCGHSA enrichment
  8. 2026-07-15 21:05 UTCGHSA enrichment
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 09:14 UTCGHSA enrichment
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-14 21:24 UTCGHSA enrichment
  14. 2026-07-14 09:34 UTCGHSA enrichment
  15. 2026-07-13 21:43 UTCEG score recompute
  16. 2026-07-13 21:42 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62195?
CVE-2026-62195 is a high vulnerability published on July 13, 2026. OpenClaw versions 2026.5.20 before 2026.6.6 contain an authorization bypass vulnerability in the MCP loopback feature that allows lower-trust callers to execute owner-only tools. Attackers can bypass authorization checks through configured input paths to execute or persist actions beyond their…
When was CVE-2026-62195 disclosed?
CVE-2026-62195 was first published in the National Vulnerability Database on July 13, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62195 actively exploited?
CVE-2026-62195 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 86.0% of all scored CVEs.
What is the CVSS score of CVE-2026-62195?
CVE-2026-62195 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-62195?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62195, 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-62195

Explore →

Is Your Infrastructure Affected by CVE-2026-62195?

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

Start Free Scan →Browse All CVEs