dbcve.org
OpenclawApplication

CVE-2026-28454

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-05
Fix available
A fix is available. Upgrade to 2026.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenClaw fails to validate webhook secrets in Telegram webhook mode, allowing unauthenticated attackers to send HTTP POST requests with attacker-controlled JSON payloads to the webhook endpoint. Attackers can spoof message.from.id and chat.id fields to bypass sender allowlists and execute privileged bot commands.

MitigationImplement HMAC signature validation for Telegram webhook requests using the configured webhook secret before processing any payload data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenclawApplication
Affected:< 2026.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenClaw version
    Locate the OpenClaw installation and check its version number (typically in a version file, --version output, or application metadata). Compare against the affected range: < 2026.2.2
    Affected if The installed version is before 2026.2.2
  2. Determine if Telegram webhook mode is enabled
    Examine the OpenClaw configuration files or settings for Telegram bot integration. Look for webhook-related configuration (often in config.yaml, settings.json, or environment variables). Check if Telegram webhook endpoint is configured and active.
    Affected if Telegram webhook mode is enabled and receiving HTTP POST requests from Telegram servers
  3. Verify webhook secret validation configuration
    Inspect the configuration for Telegram webhook endpoints. Locate the webhook secret or token validation settings. Check if a webhook secret is defined and properly validated on incoming requests.
    Affected if Webhook secret validation is not configured, disabled, or improperly enforced for Telegram webhook endpoints
  4. Review Telegram bot command permissions
    Examine the bot command configuration to identify privileged or critical severity commands. Check the sender allowlist settings that rely on message.from.id and chat.id fields for authorization.
    Affected if Privileged bot commands exist and sender allowlists rely on Telegram message fields without additional secret validation

A user is affected if OpenClaw version is below 2026.2.2 AND Telegram webhook mode is enabled AND webhook secret validation is not properly enforced, allowing unauthenticated attackers to spoof Telegram message fields and execute privileged commands.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026.2.2 or later
Fixed in 2026.2.2
Vendor patch github.com →
Interim mitigation

Implement HMAC signature validation for Telegram webhook requests using the configured webhook secret before processing any payload data.

Recommended fix High confidence

2026.2.2

  1. Backup your current Openclaw installation and configuration
  2. Upgrade Openclaw to version 2026.2.2 or later from the official repository
  3. After upgrading, verify that Telegram webhook mode now validates webhook secrets before processing any incoming requests
  4. Confirm that the webhook endpoint rejects requests with invalid or missing secrets
  5. Test that legitimate Telegram webhook requests with valid signatures are processed correctly
  6. If using a sender allowlist, verify that the fix correctly enforces it after the upgrade (the vulnerability allowed bypassing allowlists via spoofed message.from.id and chat.id fields)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28454 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28454 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data