CVE-2026-28454
Published: 05 March 2026
Summary
CVE-2026-28454 is a high-severity Insufficient Verification of Data Authenticity (CWE-345) vulnerability in Openclaw Openclaw. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 11.7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Threat & Defense at a Glance
Threat & Defense Details
Likely Mitigating ControlsAI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Directly requires independent verification of matching output before adverse decisions, mitigating insufficient authenticity checks on data from external sources.
Use of approved PKI certificates provides verifiable data authenticity and origin for communications and artifacts.
Mandates provision of authenticity and integrity artifacts that enable verification of name/address resolution data.
Requires explicit verification of data authenticity from authoritative sources, preventing acceptance of unauthenticated resolution responses.
Control requires verification of data authenticity/integrity (e.g., checksums) after aggregation/packing, directly reducing exploitation of insufficient verification before transmission.
Time synchronization supports reliable freshness verification when checking data authenticity across systems or components.
Mandates verification of data authenticity for software, firmware, and information.
Provenance documentation and monitoring directly enables verification of authenticity for components and data throughout their history.
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vuln enables remote unauth exploitation of exposed webhook (T1190) to bypass allowlists and execute privileged bot commands (T1059).
NVD Description
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…
more
and chat.id fields to bypass sender allowlists and execute privileged bot commands.
Deeper analysisAI
CVE-2026-28454 affects OpenClaw versions prior to 2026.2.2, specifically in Telegram webhook mode, which must be explicitly enabled. The vulnerability stems from a failure to validate webhook secrets, permitting unauthenticated HTTP POST requests to the webhook endpoint that processes attacker-controlled JSON payloads without verification. This issue, classified under CWE-345 (Insufficient Verification of Data Authenticity), has a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), highlighting high integrity impact from network-accessible exploitation with low complexity and no privileges required.
Remote, unauthenticated attackers can exploit this by sending crafted HTTP POST requests to the exposed webhook endpoint, forging Telegram update payloads. By spoofing fields such as message.from.id and chat.id, attackers bypass sender allowlists, enabling execution of privileged bot commands that would otherwise be restricted.
Mitigation details are outlined in the GitHub security advisory (GHSA-fhvm-j76f-qmjv) and related commits, which patch the validation of webhook secrets. Security practitioners should upgrade to OpenClaw version 2026.2.2 or later, where the commits (3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930, 5643a934799dc523ec2ef18c007e1aa2c386b670, 633fe8b9c17f02fcc68ecdb5ec212a5ace932f09, ca92597e1f9593236ad86810b66633144b69314d) address the flaw by enforcing proper secret checks in Telegram webhook mode.
Details
- CWE(s)