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.8EG
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.8Exploit: None knownExposed: 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 PROB
0%
EPSS %ILE
23%
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 17× in last 7d / 95× 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 228 total refreshes for this CVE.

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

Related CVEs(same CWE)

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 0% probability of exploitation in the next 30 days, which ranks it in the top 76.6% of all scored CVEs.
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