CVE-2026-53807

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-11. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
Trending — 3 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

OpenClaw before 2026.5.6 contains an authorization bypass vulnerability in Telegram interactive callbacks that allows authenticated users to skip commands.allowFrom validation. Attackers can invoke affected callbacks to mark themselves as authorized senders before allowlist checks are applied, triggering command behavior outside configured Telegram sender restrictions.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
23.4%
KEV
Not listed

Published

June 11, 2026

Last Modified

June 23, 2026

Advisory Details (2)

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

OpenClaw < 2026.5.6 - Authorization Bypass in Telegram Interactive Callbacks via commands.allowFrom | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-authorization-bypass-in-telegram-interactive-callbacks-via-commands-allowfrom
github Patch Available

Telegram interactive callbacks could skip commands.allowFrom · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-w5ww-7chg-mxcq

Vendor Advisories for CVE-2026-53807(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.6—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 85× 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.

Showing the most recent 100 of 127 total refreshes for this CVE.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:19 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 23:34 UTCGHSA enrichment
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-16 10:34 UTCGHSA enrichment
  11. 2026-07-15 21:33 UTCGHSA enrichment
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 07:57 UTCGHSA enrichment
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-14 15:23 UTCGHSA enrichment
  18. 2026-07-14 02:23 UTCGHSA enrichment
  19. 2026-07-13 22:31 UTCEPSS rescore
  20. 2026-07-13 13:23 UTCGHSA enrichment
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-12 23:53 UTCGHSA enrichment
  24. 2026-07-12 10:53 UTCGHSA enrichment
  25. 2026-07-12 05:46 UTCEPSS rescore
Show 75 more
  1. 2026-07-11 21:34 UTCGHSA enrichment
  2. 2026-07-11 08:34 UTCGHSA enrichment
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-10 19:33 UTCGHSA enrichment
  6. 2026-07-10 06:33 UTCGHSA enrichment
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 13:28 UTCGHSA enrichment
  10. 2026-07-08 23:48 UTCGHSA enrichment
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-08 10:48 UTCGHSA enrichment
  14. 2026-07-07 21:37 UTCGHSA enrichment
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 01:29 UTCGHSA enrichment
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 02:31 UTCGHSA enrichment
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-05 13:23 UTCGHSA enrichment
  24. 2026-07-05 02:31 UTCEPSS rescore
  25. 2026-07-05 02:30 UTCEPSS rescore
  26. 2026-07-05 00:17 UTCGHSA enrichment
  27. 2026-07-04 11:15 UTCGHSA enrichment
  28. 2026-07-04 06:31 UTCEPSS rescore
  29. 2026-07-04 06:31 UTCEPSS rescore
  30. 2026-07-03 20:45 UTCGHSA enrichment
  31. 2026-07-03 07:40 UTCGHSA enrichment
  32. 2026-07-02 17:34 UTCGHSA enrichment
  33. 2026-07-02 04:32 UTCGHSA enrichment
  34. 2026-07-01 15:33 UTCGHSA enrichment
  35. 2026-07-01 15:07 UTCEPSS rescore
  36. 2026-07-01 02:32 UTCGHSA enrichment
  37. 2026-06-30 23:22 UTCEPSS rescore
  38. 2026-06-30 13:32 UTCGHSA enrichment
  39. 2026-06-29 21:05 UTCGHSA enrichment
  40. 2026-06-29 14:06 UTCEPSS rescore
  41. 2026-06-29 14:06 UTCEPSS rescore
  42. 2026-06-29 08:06 UTCGHSA enrichment
  43. 2026-06-28 18:52 UTCGHSA enrichment
  44. 2026-06-28 14:07 UTCEPSS rescore
  45. 2026-06-28 05:52 UTCGHSA enrichment
  46. 2026-06-28 04:56 UTCEPSS rescore
  47. 2026-06-28 04:56 UTCEPSS rescore
  48. 2026-06-27 16:48 UTCGHSA enrichment
  49. 2026-06-27 03:48 UTCGHSA enrichment
  50. 2026-06-27 03:08 UTCEPSS rescore
  51. 2026-06-26 14:49 UTCGHSA enrichment
  52. 2026-06-26 01:40 UTCGHSA enrichment
  53. 2026-06-25 13:49 UTCEPSS rescore
  54. 2026-06-25 12:39 UTCGHSA enrichment
  55. 2026-06-24 23:39 UTCGHSA enrichment
  56. 2026-06-24 14:05 UTCEPSS rescore
  57. 2026-06-24 10:39 UTCGHSA enrichment
  58. 2026-06-23 21:33 UTCEPSS rescore
  59. 2026-06-23 21:33 UTCEPSS rescore
  60. 2026-06-23 21:24 UTCGHSA enrichment
  61. 2026-06-23 08:20 UTCGHSA enrichment
  62. 2026-06-22 19:14 UTCGHSA enrichment
  63. 2026-06-22 14:25 UTCEPSS rescore
  64. 2026-06-22 14:25 UTCEPSS rescore
  65. 2026-06-22 05:51 UTCGHSA enrichment
  66. 2026-06-21 16:50 UTCGHSA enrichment
  67. 2026-06-21 14:56 UTCEPSS rescore
  68. 2026-06-21 14:56 UTCEPSS rescore
  69. 2026-06-21 03:41 UTCGHSA enrichment
  70. 2026-06-21 01:59 UTCEPSS rescore
  71. 2026-06-21 01:59 UTCEPSS rescore
  72. 2026-06-20 14:37 UTCGHSA enrichment
  73. 2026-06-20 01:34 UTCGHSA enrichment
  74. 2026-06-19 19:26 UTCEPSS rescore
  75. 2026-06-19 19:26 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-53807?
CVE-2026-53807 is a high vulnerability published on June 11, 2026. OpenClaw before 2026.5.6 contains an authorization bypass vulnerability in Telegram interactive callbacks that allows authenticated users to skip commands.allowFrom validation. Attackers can invoke affected callbacks to mark themselves as authorized senders before allowlist checks are applied,…
When was CVE-2026-53807 disclosed?
CVE-2026-53807 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-53807 actively exploited?
CVE-2026-53807 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53807?
CVE-2026-53807 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53807?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53807, 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-53807

Explore →

Is Your Infrastructure Affected by CVE-2026-53807?

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

Start Free Scan →Browse All CVEs