CVE-2026-28454: openclaw (npm)

Should you act?

Normal patch cycle

No exploitation signal; fix it in your next routine update if you are affected. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
EPSS 0.4%, percentile 34: FIRST’s model estimates a 0.4% chance of exploitation activity in the next 30 days, higher than 34% of all scored CVEs (low). EPSS is a probability, not a verdict.
Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
Only applies if your dependency tree includes openclaw (npm) < 2026.2.1, fixed in 2026.2.1. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

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.2.1

Impact

Weakness type: CWE-345, CWE-285.

Product: openclaw (npm) · Assigned by: VulnCheck · Published: 2026-03-05

Affected and fixed versions

Ecosystem	Package	Vulnerable	First fixed
npm	`openclaw`	< 2026.2.1	2026.2.1

Vendor	Product	Affected versions (per CVE record)
OpenClaw	OpenClaw	< 2026.2.2

Severity scores

Scored by	CVSS	Score	Vector
VulnCheck	4.0	8.2 High	`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`
VulnCheck	3.1	7.5 High	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`
GitHub	4.0	9.1	`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`

Attack vector: network (remotely reachable)
Attack complexity: low
Attack requirements: present (depends on deployment conditions)
Privileges required: none (no login)
User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
CISA SSVC assessment: exploitation none, automatable yes, technical impact partial.
FIRST EPSS (model of 2026-10-21): 0.41% probability of exploitation activity in the next 30 days; percentile 34.

Timeline

2026-02-17 — GitHub-reviewed advisory GHSA-fhvm-j76f-qmjv published (critical)
2026-03-05 — CVE record published by VulnCheck
2026-03-09 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.