CVE-2026-53857

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

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

OpenClaw before 2026.5.3 contains a policy enforcement vulnerability where Zalo contacts with mutable display metadata could match allowFrom policy entries through display name changes. Attackers with mutable display names could receive agent responses intended for different Zalo identities when the feature is enabled.

CVSS v3
8.1
EG Score
8.1(high)
EPSS
13.1%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 18, 2026

Advisory Details (2)

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

OpenClaw < 2026.5.3 - Mutable Display Name Binding in Zalo allowFrom Policy | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-mutable-display-name-binding-in-zalo-allowfrom-policy
github Patch Available

Zalo allowFrom could bind to mutable display names · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-8c59-hr4w-qg69

Vendor Advisories for CVE-2026-53857(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
openclaw—2026.5.3—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53857?
CVE-2026-53857 is a high vulnerability published on June 16, 2026. OpenClaw before 2026.5.3 contains a policy enforcement vulnerability where Zalo contacts with mutable display metadata could match allowFrom policy entries through display name changes. Attackers with mutable display names could receive agent responses intended for different Zalo identities when…
When was CVE-2026-53857 disclosed?
CVE-2026-53857 was first published in the National Vulnerability Database on June 16, 2026, with the most recent update on June 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53857 actively exploited?
CVE-2026-53857 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53857?
CVE-2026-53857 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-53857?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53857, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53857

Explore →

Is Your Infrastructure Affected by CVE-2026-53857?

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

Start Free Scan →Browse All CVEs