CVE-2026-53813

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:vulncheck, epss
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

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

OpenClaw before 2026.4.25 contains a path traversal vulnerability in memory-core artifact loading where workspace state influences local package root resolution. Attackers with access to affected workspaces can load memory-core artifacts from unintended local locations, potentially executing malicious code or accessing sensitive data.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
1.8%
KEV
Not listed

Published

June 11, 2026

Last Modified

June 23, 2026

Advisory Details (2)

Auto-updated Jun 11, 2026
Patch available. Sources: github.
generic

OpenClaw < 2026.4.25 - Arbitrary Artifact Loading via Fake Package Root Resolution | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-arbitrary-artifact-loading-via-fake-package-root-resolution
github Patch Available

Fake package roots could influence memory-core artifact loading · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-v8cx-933x-r976

Vendor Advisories for CVE-2026-53813(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 20× in last 7d / 81× 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-07 01:38 UTCEG score recompute
  2. 2026-07-06 02:40 UTCEG score recompute
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 13:34 UTCEG score recompute
  6. 2026-07-05 02:31 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-05 00:28 UTCEG score recompute
  9. 2026-07-04 11:17 UTCEG score recompute
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 20:47 UTCEG score recompute
  13. 2026-07-03 07:41 UTCEG score recompute
  14. 2026-07-02 17:56 UTCEG score recompute
  15. 2026-07-02 04:50 UTCEG score recompute
  16. 2026-07-01 15:45 UTCEG score recompute
  17. 2026-07-01 15:07 UTCEPSS rescore
  18. 2026-07-01 02:38 UTCEG score recompute
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-30 13:32 UTCEG score recompute
  21. 2026-06-30 00:25 UTCEG score recompute
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 11:20 UTCEG score recompute
  25. 2026-06-28 22:14 UTCEG score recompute
Show 56 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 09:08 UTCEG score recompute
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-27 20:04 UTCEG score recompute
  6. 2026-06-27 06:59 UTCEG score recompute
  7. 2026-06-27 03:08 UTCEPSS rescore
  8. 2026-06-26 17:53 UTCEG score recompute
  9. 2026-06-26 04:46 UTCEG score recompute
  10. 2026-06-25 15:41 UTCEG score recompute
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-25 02:34 UTCEG score recompute
  13. 2026-06-24 13:28 UTCEG score recompute
  14. 2026-06-24 00:05 UTCEG score recompute
  15. 2026-06-23 21:33 UTCEPSS rescore
  16. 2026-06-23 21:33 UTCEPSS rescore
  17. 2026-06-23 11:00 UTCEG score recompute
  18. 2026-06-22 21:54 UTCEG score recompute
  19. 2026-06-22 14:25 UTCEPSS rescore
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-22 08:31 UTCEG score recompute
  22. 2026-06-21 19:05 UTCEG score recompute
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 04:58 UTCEG score recompute
  26. 2026-06-21 01:59 UTCEPSS rescore
  27. 2026-06-21 01:59 UTCEPSS rescore
  28. 2026-06-20 15:50 UTCEG score recompute
  29. 2026-06-20 02:43 UTCEG score recompute
  30. 2026-06-19 19:26 UTCEPSS rescore
  31. 2026-06-19 19:26 UTCEPSS rescore
  32. 2026-06-19 13:38 UTCEG score recompute
  33. 2026-06-19 00:30 UTCEG score recompute
  34. 2026-06-18 17:52 UTCEPSS rescore
  35. 2026-06-18 17:52 UTCEPSS rescore
  36. 2026-06-18 11:24 UTCEG score recompute
  37. 2026-06-17 22:17 UTCEG score recompute
  38. 2026-06-17 17:53 UTCEPSS rescore
  39. 2026-06-17 09:01 UTCEG score recompute
  40. 2026-06-16 19:53 UTCEG score recompute
  41. 2026-06-16 06:48 UTCEG score recompute
  42. 2026-06-15 17:49 UTCEPSS rescore
  43. 2026-06-15 17:49 UTCEPSS rescore
  44. 2026-06-15 17:43 UTCEG score recompute
  45. 2026-06-15 04:32 UTCEG score recompute
  46. 2026-06-14 23:18 UTCEPSS rescore
  47. 2026-06-14 15:27 UTCEG score recompute
  48. 2026-06-14 02:21 UTCEG score recompute
  49. 2026-06-13 23:00 UTCEPSS rescore
  50. 2026-06-13 13:16 UTCEG score recompute
  51. 2026-06-13 00:09 UTCEG score recompute
  52. 2026-06-12 23:12 UTCEPSS rescore
  53. 2026-06-12 23:12 UTCEPSS rescore
  54. 2026-06-12 11:02 UTCEG score recompute
  55. 2026-06-11 21:57 UTCEG score recompute
  56. 2026-06-11 21:57 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53813?
CVE-2026-53813 is a high vulnerability published on June 11, 2026. OpenClaw before 2026.4.25 contains a path traversal vulnerability in memory-core artifact loading where workspace state influences local package root resolution. Attackers with access to affected workspaces can load memory-core artifacts from unintended local locations, potentially executing…
When was CVE-2026-53813 disclosed?
CVE-2026-53813 was first published in the National Vulnerability Database on June 11, 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-53813 actively exploited?
CVE-2026-53813 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53813?
CVE-2026-53813 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53813?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53813, 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-53813

Explore →

Is Your Infrastructure Affected by CVE-2026-53813?

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

Start Free Scan →Browse All CVEs