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.1- Fixed in:
>= 2026.2.2
Details
In affected versions (for example 2026.2.1), the inbound allowlist check in extensions/voice-call/src/manager.ts used suffix-based matching and accepted empty caller IDs after normalization.
This allowed two bypasses:
- Missing/empty
fromvalues normalized to an empty string, which caused the allowlist predicate to evaluate as allowed. - Suffix-based matching meant any caller number whose digits ended with an allowlisted number would be accepted.
Proof Of Concept
- Configure the voice-call extension with
inboundPolicy: allowlistandallowFrom: ["+15550001234"]. - Place/trigger an inbound call with missing/empty caller ID (provider-dependent; for example anonymous/restricted caller). The call is accepted.
- Place a call from a number whose E.164 digits end with
15550001234(for example+99915550001234). The call is accepted.
Impact
Only operators who install/enable the optional voice-call extension and use inboundPolicy=allowlist or pairing could have inbound access controls bypassed, potentially allowing unauthorized callers to reach auto-response and tool execution.
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
CVE-2026-28446 has a CVSS score of 9.4 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
The fix hardens inbound policy handling:
- Reject inbound calls when caller ID is missing.
- Require strict equality when comparing normalized caller IDs against the allowlist (no suffix/prefix matching).
- Add regression tests for missing caller ID, anonymous caller ID, and suffix-collision cases.
Fix commit(s):
f8dfd034f5d9235c5485f492a9e4ccc114e97fdb
Thanks @simecek for reporting.
Frequently Asked Questions
- What is CVE-2026-28446? CVE-2026-28446 is a critical-severity improper authentication vulnerability in openclaw (npm), affecting versions < 2026.2.2. It is fixed in 2026.2.2. The application does not adequately verify the identity of a user, device, or process before granting access.
- How severe is CVE-2026-28446? CVE-2026-28446 has a CVSS score of 9.4 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of openclaw are affected by CVE-2026-28446? openclaw (npm) versions < 2026.2.2 is affected.
- Is there a fix for CVE-2026-28446? Yes. CVE-2026-28446 is fixed in 2026.2.2. Upgrade to this version or later.
- Is CVE-2026-28446 exploitable, and should I be worried? Whether CVE-2026-28446 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-28446 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-28446? Upgrade
openclawto 2026.2.2 or later.