CVE-2026-28454: Openclaw OpenClaw Has A Potential Access-group Vulnerability

Q: What is CVE-2026-28454?

CVE-2026-28454 is a security vulnerability in Openclaw involving OpenClaw has a potential access-group authorization bypass if channel type lookup fails under CWE-345: Insufficient Verification of Data Authenticity.

Q: Which Openclaw versions are affected?

Affected versions include releases prior to 2026.2.1 across affected packages: openclaw.

Q: What version fixes CVE-2026-28454?

Upgrading to 2026.2.1 (or the latest patched release for your respective branch) resolves the vulnerability.

Q: Is openclaw affected?

Yes, openclaw is affected in releases prior to 2026.2.1. Upgrade your dependency to 2026.2.1 or later.

Q: What is the CVSS score of CVE-2026-28454?

CVE-2026-28454 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Q: What CWE is associated with CVE-2026-28454?

CVE-2026-28454 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).

Q: How can I check npm dependencies for CVE-2026-28454?

Run the dependency tree command: 'npm ls openclaw'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.

CRITICAL

Advisory Identifier: GHSA-fhvm-j76f-qmjv

CVSS 9.8

CWE-345 CWE-285

Published 2026-02-17

Advisory Summary

CVE-2026-28454 is a CRITICAL (CVSS 9.8) openclaw has a potential access-group vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting Openclaw libraries in the npm ecosystem. The issue involves openclaw has a potential access-group authorization bypass if channel type lookup fails. Remediation is available by upgrading affected packages to version 2026.2.1.

CVE-2026-28454 at a Glance

CVE Identifier CVE-2026-28454

GHSA Identifier GHSA-fhvm-j76f-qmjv

Severity CRITICAL

CVSS v3.1 Base Score 9.8

CWE Classification CWE-345: Insufficient Verification of Data Authenticity

Affected Product Openclaw

Package Ecosystem npm

Published Date 2026-02-17

Last Updated 2026-03-06

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)

Attack Complexity Low (AC:L)

Privileges Required None (PR:N)

User Interaction None (UI:N)

Scope Unchanged (S:U)

Confidentiality High (C:H)

Integrity High (I:H)

Availability High (A:H)

How to Fix CVE-2026-28454

To remediate this vulnerability, upgrade all affected Openclaw dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openclaw fixed: 2026.2.1

npm install openclaw@2026.2.1

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls openclaw

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-28454, inspect your project dependencies using npm:

npm ls openclaw

Analyze the terminal output to locate any version of Openclaw in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.2.1), your application is affected.

Note: The npm ls openclaw command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In Openclaw, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary When Telegram webhook mode is enabled without a configured webhook secret, OpenClaw may accept unauthenticated HTTP POST requests at the Telegram webhook endpoint and trust attacker-controlled update JSON. This can allow forged Telegram updates that spoof `message.from.id` / `chat.id`, potentially bypassing sender allowlists and executing privileged bot commands. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: `<= 2026.1.30` - Patched: `>= 2026.2.1` ## Impact An attacker who can reach the webhook endpoint can forge Telegram updates and impersonate allowlisted/paired senders by spoofing fields in the webhook payload (for example `message.from.id`). Impact depends on enabled commands/tools and the deployment’s network exposure. ## Mitigations / Workarounds - Configure a strong `channels.telegram.webhookSecret` and ensure your reverse proxy forwards the `X-Telegram-Bot-Api-Secret-Token` header unchanged. ## Fix Commit(s) - ca92597e1f9593236ad86810b66633144b69314d (config validation: `webhookUrl` requires `webhookSecret`) Defense-in-depth / supporting fixes: - 5643a934799dc523ec2ef18c007e1aa2c386b670 (default webhook listener bind host to loopback) - 3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930 (bound webhook request body size/time) - 633fe8b9c17f02fcc68ecdb5ec212a5ace932f09 (runtime guard: reject webhook startup when secret is missing/empty) ## Release Process Note `patched_versions` is set to the first fixed release (`2026.2.1`). Thanks @yueyueL for reporting.

CVE-2026-28454 Affected Openclaw Versions

1 component(s)

Fixed Versions:

2026.2.1

Product / Package	Ecosystem	Affected Versions	Fixed Version
openclaw npm/openclaw	npm	< 2026.2.1	2026.2.1

References

GitHub Advisory / Wiki ADVISORY

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

NVD — CVE-2026-28454 NVD

https://nvd.nist.gov/vuln/detail/CVE-2026-28454

Security Fix Commit FIX COMMIT

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

Security Fix Commit FIX COMMIT

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

Security Fix Commit FIX COMMIT

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

Security Fix Commit FIX COMMIT

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

Openclaw Source Repository REPOSITORY

https://github.com/openclaw/openclaw

Openclaw Release RELEASE

https://github.com/openclaw/openclaw/releases/tag/v2026.2.1

www.vulncheck.com/advisories/openclaw... WEB

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

Frequently Asked Questions

What is CVE-2026-28454?

CVE-2026-28454 is a security vulnerability in Openclaw involving OpenClaw has a potential access-group authorization bypass if channel type lookup fails under CWE-345: Insufficient Verification of Data Authenticity.

Which Openclaw versions are affected?

Affected versions include releases prior to 2026.2.1 across affected packages: openclaw.

What version fixes CVE-2026-28454?

Upgrading to 2026.2.1 (or the latest patched release for your respective branch) resolves the vulnerability.

Is openclaw affected?

Yes, openclaw is affected in releases prior to 2026.2.1. Upgrade your dependency to 2026.2.1 or later.

What is the CVSS score of CVE-2026-28454?

CVE-2026-28454 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

What CWE is associated with CVE-2026-28454?

CVE-2026-28454 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).

How can I check npm dependencies for CVE-2026-28454?

Run the dependency tree command: 'npm ls openclaw'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.

Machine-readable OSV JSON OSV v1.5 Schema

Normalized schema output

View Raw JSON

{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fhvm-j76f-qmjv",
  "modified" : "2026-03-06T00:58:46Z",
  "published" : "2026-02-17T21:34:36Z",
  "aliases" : [ "CVE-2026-28454" ],
  "summary" : "OpenClaw has a potential access-group authorization bypass if channel type lookup fails",
  "details" : "## Summary\n\nWhen Telegram webhook mode is enabled without a configured webhook secret, OpenClaw may accept unauthenticated HTTP POST requests at the Telegram webhook endpoint and trust attacker-controlled update JSON. This can allow forged Telegram updates that spoof `message.from.id` / `chat.id`, potentially bypassing sender allowlists and executing privileged bot commands.\n\n## Affected Packages / Versions\n\n- Package: `openclaw` (npm)\n- Affected: `<= 2026.1.30`\n- Patched: `>= 2026.2.1`\n\n## Impact\n\nAn attacker who can reach the webhook endpoint can forge Telegram updates and impersonate allowlisted/paired senders by spoofing fields in the webhook payload (for example `message.from.id`). Impact depends on enabled commands/tools and the deployment’s network exposure.\n\n## Mitigations / Workarounds\n\n- Configure a strong `channels.telegram.webhookSecret` and ensure your reverse proxy forwards the `X-Telegram-Bot-Api-Secret-Token` header unchanged.\n\n## Fix Commit(s)\n\n- ca92597e1f9593236ad86810b66633144b69314d (config validation: `webhookUrl` requires `webhookSecret`)\n\nDefense-in-depth / supporting fixes:\n\n- 5643a934799dc523ec2ef18c007e1aa2c386b670 (default webhook listener bind host to loopback)\n- 3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930 (bound webhook request body size/time)\n- 633fe8b9c17f02fcc68ecdb5ec212a5ace932f09 (runtime guard: reject webhook startup when secret is missing/empty)\n\n## Release Process Note\n\n`patched_versions` is set to the first fixed release (`2026.2.1`).\n\nThanks @yueyueL for reporting.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "openclaw"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.2.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/security/advisories/GHSA-fhvm-j76f-qmjv"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-28454"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/5643a934799dc523ec2ef18c007e1aa2c386b670"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/633fe8b9c17f02fcc68ecdb5ec212a5ace932f09"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/ca92597e1f9593236ad86810b66633144b69314d"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openclaw/openclaw"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/releases/tag/v2026.2.1"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/openclaw-authorization-bypass-via-unauthenticated-telegram-webhook"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-285", "CWE-345" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-17T21:34:36Z",
    "nvd_published_at" : "2026-03-05T22:16:17Z"
  }
}

CVSS V3

9.8 CRITICAL

Attack Vector Network (AV:N)

Attack Complexity Low (AC:L)

Privileges Required None (PR:N)

User Interaction None (UI:N)

Scope Unchanged (S:U)

Confidentiality High (C:H)

Integrity High (I:H)

Availability High (A:H)

Vector String

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

Advisory Metadata

Source ID: GHSA-fhvm-j76f-qmjv
Schema Version: 1.4.0
Published: 2026-02-17 21:34
Last Modified: 2026-03-06 00:58
Database Record File: advisories/github-reviewed/2026/02/GHSA-fhvm-j76f-qmjv/GHSA-fhvm-j76f-qmjv.json