CVE-2026-28454

CRITICALNVD 9.89.8
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: nvd
9.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: 9.8Exploit: None knownExposed: 0

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

OpenClaw versions prior to 2026.2.2 fail to validate webhook secrets in Telegram webhook mode (must be enabled), allowing unauthenticated HTTP POST requests to the webhook endpoint that trust attacker-controlled JSON payloads. Remote attackers can forge Telegram updates by spoofing message.from.id and chat.id fields to bypass sender allowlists and execute privileged bot commands.

CVSS v3
9.8
EG Score
9.8(low)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

March 5, 2026

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated Jul 27, 2026
Patch available. Sources: github_commit, github.
generic

OpenClaw < 2026.2.2 - Authorization Bypass via Unauthenticated Telegram Webhook | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openclaw-authorization-bypass-via-unauthenticated-telegram-webhook
github Patch Available

Potential access-group authorization bypass if channel type lookup fails · Advisory · openclaw/openclaw · GitHub

https://github.com/openclaw/openclaw/security/advisories/GHSA-fhvm-j76f-qmjv
github_commit

commit ca92597e1f95 (openclaw/openclaw)

Fix landed in openclaw/openclaw commit ca92597e1f95 — awaiting tagged release

https://github.com/openclaw/openclaw/commit/ca92597e1f9593236ad86810b66633144b69314d
github_commit

commit 633fe8b9c17f (openclaw/openclaw)

Fix landed in openclaw/openclaw commit 633fe8b9c17f — awaiting tagged release

https://github.com/openclaw/openclaw/commit/633fe8b9c17f02fcc68ecdb5ec212a5ace932f09
github_commit

commit 5643a934799d (openclaw/openclaw)

Fix landed in openclaw/openclaw commit 5643a934799d — awaiting tagged release

https://github.com/openclaw/openclaw/commit/5643a934799dc523ec2ef18c007e1aa2c386b670
github_commit

commit 3cbcba10cf30 (openclaw/openclaw)

Fix landed in openclaw/openclaw commit 3cbcba10cf30 — awaiting tagged release

https://github.com/openclaw/openclaw/commit/3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 1× in last 7d / 1× 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-27 13:50 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-28454?
CVE-2026-28454 is a critical vulnerability published on March 5, 2026. OpenClaw versions prior to 2026.2.2 fail to validate webhook secrets in Telegram webhook mode (must be enabled), allowing unauthenticated HTTP POST requests to the webhook endpoint that trust attacker-controlled JSON payloads. Remote attackers can forge Telegram updates by spoofing message.from.id…
When was CVE-2026-28454 disclosed?
CVE-2026-28454 was first published in the National Vulnerability Database on March 5, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-28454 actively exploited?
CVE-2026-28454 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 83.0% of all scored CVEs.
What is the CVSS score of CVE-2026-28454?
CVE-2026-28454 has a CVSS v3 base score of 9.8 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-28454?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-28454, 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-28454

Explore →

Is Your Infrastructure Affected by CVE-2026-28454?

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

Start Free Scan →Browse All CVEs