CVE-2026-28446: openclaw (npm)

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. 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 1.0%, percentile 63: FIRST’s model estimates a 1.0% chance of exploitation activity in the next 30 days, higher than 63% of all scored CVEs (moderate). 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.2, fixed in 2026.2.2. Check your lockfile, including transitive dependencies.

What it is

OpenClaw versions prior to 2026.2.1 with the voice-call extension installed and enabled contain an authentication bypass vulnerability in inbound allowlist policy validation that accepts empty caller IDs and uses suffix-based matching instead of strict equality. Remote attackers can bypass inbound access controls by placing calls with missing caller IDs or numbers ending with allowlisted digits to reach the voice-call agent and execute tools.

From the GitHub advisory

Summary

An authentication bypass in the optional voice-call extension/plugin allowed unapproved or anonymous callers to reach the voice-call agent when inbound policy was set to allowlist or pairing.

Deployments that do not install/enable the voice-call extension are not affected.

Affected Packages / Versions

- openclaw (npm): = 2026.2.2

Weakness type: CWE-303, CWE-287.

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

Affected and fixed versions

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

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

Severity scores

Scored by	CVSS	Score	Vector
VulnCheck	4.0	9.2 Critical	`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`
VulnCheck	3.1	9.4 Critical	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`
GitHub	4.0	9.2	`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X`

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 total.
FIRST EPSS (model of 2026-10-21): 1.02% probability of exploitation activity in the next 30 days; percentile 63.

Timeline

2026-02-17 — GitHub-reviewed advisory GHSA-4rj2-gpmh-qq5x published (critical)
2026-03-05 — CVE record published by VulnCheck
2026-03-11 — CVE record last updated

Sources and references

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