CVE-2026-28465: OpenClaw optional voice-call plugin: webhook verification may be bypassed behind certain proxy configurations
Affected Packages / Versions This issue affects the optional voice-call plugin only. It is not enabled by default; it only applies to installations where the plugin is installed and enabled. - Package: @openclaw/voice-call - Vulnerable versions: = 2026.2.3 Legacy package name (if you are still using it): - Package: @clawdbot/voice-call - Vulnerable versions: <= 2026.1.24 - Patched versions: none published under this…
Published Feb 17, 2026 · Updated Mar 9, 2026
Affected packages
@openclaw/voice-call
- Ecosystem
- npm
- Affected
- < 2026.2.3
- Fixed in
- 2026.2.3
- Check
npm ls @openclaw/voice-call
@clawdbot/voice-call
- Ecosystem
- npm
- Affected
- <= 2026.1.24
- Fixed in
- No patched version yet
- Check
npm ls @clawdbot/voice-call
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Affected Packages / Versions
This issue affects the optional voice-call plugin only. It is not enabled by default; it only applies to installations where the plugin is installed and enabled.
- Package:
@openclaw/voice-call - Vulnerable versions:
< 2026.2.3 - Patched versions:
>= 2026.2.3
Legacy package name (if you are still using it):
- Package:
@clawdbot/voice-call - Vulnerable versions:
<= 2026.1.24 - Patched versions: none published under this package name; migrate to
@openclaw/voice-call
Summary
In certain reverse-proxy / forwarding setups, webhook verification can be bypassed if untrusted forwarded headers are accepted.
Impact
An external party may be able to send voice-call webhook requests that are accepted as valid, which can result in spoofed webhook events being processed.
Root Cause
Some deployments implicitly trusted forwarded headers (for example Forwarded / X-Forwarded-*) when determining request properties used during webhook verification. If those headers are not overwritten by a trusted proxy, a client can supply them directly and influence verification.
Resolution
Ignore forwarded headers by default unless explicitly trusted and allowlisted in configuration. Keep any loopback-only development bypass restricted to local development only. Upgrade to a patched version.
If you cannot upgrade immediately, strip Forwarded and X-Forwarded-* headers at the edge so clients cannot supply them directly.
Fix Commit(s)
a749db9820eb6d6224032a5a34223d286d2dcc2f
Credits
Thanks @0x5t for reporting.
Credited to 0x5t.
References
- https://github.com/openclaw/openclaw/security/advisories/GHSA-3m3q-x3gj-f79x
- https://github.com/openclaw/openclaw/commit/a749db9820eb6d6224032a5a34223d286d2dcc2f
- https://github.com/openclaw/openclaw/releases/tag/v2026.2.3
- https://nvd.nist.gov/vuln/detail/CVE-2026-28465
- https://www.vulncheck.com/advisories/openclaw-voice-call-webhook-verification-bypass-via-forwarded-headers
- https://github.com/advisories/GHSA-3m3q-x3gj-f79x
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
