CVE-2026-62219

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

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

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

OpenClaw 2026.2.12 before 2026.5.26 contain an authorization bypass vulnerability in the hooks allowedAgentIds validation. A lower-trust caller or configured input path can bypass agent ID restrictions by submitting blank agent IDs, allowing actions that should require stronger authorization or policy checks.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
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.2.12 < 2026.5.26 Authorization Bypass via Blank Agent IDs | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-authorization-bypass-via-blank-agent-ids
github Patch Available

Hooks allowedAgentIds could be bypassed with blank agent IDs · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-724r-v4wf-mqc5

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62219?
CVE-2026-62219 is a high vulnerability published on July 17, 2026. OpenClaw 2026.2.12 before 2026.5.26 contain an authorization bypass vulnerability in the hooks allowedAgentIds validation. A lower-trust caller or configured input path can bypass agent ID restrictions by submitting blank agent IDs, allowing actions that should require stronger authorization or…
When was CVE-2026-62219 disclosed?
CVE-2026-62219 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-62219 actively exploited?
CVE-2026-62219 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 93.0% of all scored CVEs.
What is the CVSS score of CVE-2026-62219?
CVE-2026-62219 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-62219?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62219, 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-62219

Explore →

Is Your Infrastructure Affected by CVE-2026-62219?

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

Start Free Scan →Browse All CVEs