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.
@openclaw/voice-call< 2026.2.3>= 2026.2.3Legacy package name (if you are still using it):
@clawdbot/voice-call<= 2026.1.24@openclaw/voice-callIn certain reverse-proxy / forwarding setups, webhook verification can be bypassed if untrusted forwarded headers are accepted.
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.
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.
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.
a749db9820eb6d6224032a5a34223d286d2dcc2fThanks @0x5t for reporting.
{
"cwe_ids": [
"CWE-287",
"CWE-290",
"CWE-345"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-17T21:31:58Z",
"nvd_published_at": "2026-03-05T22:16:19Z",
"severity": "HIGH"
}