dbcve.org
OpenclawApplication

CVE-2026-28446

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
Public exploit 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.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.

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 versions before 2026.2.1 with the voice-call extension contain an authentication bypass in inbound allowlist policy validation. The vulnerability stems from the system accepting empty caller IDs and using suffix-based matching (e.g., matching '1234' against allowlist entry '234') instead of strict equality checks, allowing remote attackers to bypass inbound access controls by presenting missing caller IDs or numbers with allowlisted suffixes.

MitigationUpgrade to OpenClaw 2026.2.1 or later. Until then, disable the voice-call extension if not required, or implement compensating controls such as enforcing strict caller ID validation at the telephony gateway level and logging all inbound call attempts for monitoring.

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 retrieve its version number (typically via --version flag, package manager, or application metadata)
    Affected if Version is less than 2026.2.2
  2. Confirm voice-call extension is enabled
    Check the OpenClaw configuration or extension status to determine if the voice-call extension is currently active
    Affected if Voice-call extension is enabled and version is vulnerable
  3. Review inbound allowlist policy configuration
    Examine the inbound allowlist policy settings in OpenClaw to identify any configured caller ID allowlist entries
    Affected if An inbound allowlist policy with caller ID entries exists and the voice-call extension is enabled
  4. Test for empty caller ID acceptance
    Inspect logs or test inbound calls with no caller ID presented to see if the system accepts and processes them
    Affected if The system accepts and processes calls with missing or empty caller IDs when an allowlist policy exists
  5. Verify allowlist matching logic
    Review configuration or logs to determine whether allowlist matching uses suffix-based matching versus strict equality
    Affected if Allowlist entries match callers based on suffix (e.g., caller '1234' matches allowlist entry '234') rather than exact caller ID comparison

Environment is affected if OpenClaw version is below 2026.2.2, the voice-call extension is enabled, and an inbound allowlist policy exists that accepts empty caller IDs or uses non-strict suffix matching.

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

Upgrade to OpenClaw 2026.2.1 or later. Until then, disable the voice-call extension if not required, or implement compensating controls such as enforcing strict caller ID validation at the telephony gateway level and logging all inbound call attempts for monitoring.

Recommended fix Moderate confidence

2026.2.2 or later

  1. 1. Identify the current OpenClaw version by checking the application metadata or running 'openclaw --version'
  2. 2. Verify if the voice-call extension is installed and enabled on the system
  3. 3. Pull the latest version of OpenClaw from the official repository or package manager
  4. 4. Upgrade to version 2026.2.2 or later: 'openclaw upgrade' or download from https://github.com/openclaw/openclaw/releases
  5. 5. Alternatively, manually apply the vendor patch by cherry-picking commit f8dfd034f5d9235c5485f492a9e4ccc114e97fdb
  6. 6. After upgrade, verify the allowlist policy validation now uses strict equality matching instead of suffix-based matching
  7. 7. Confirm empty caller IDs are rejected in authentication validation

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 / QA3.0 h
19.0 hours of engineering $3,380
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28446 — 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-28446 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