How severe is CVE-2026-28465?

No CVSS score has been assigned to CVE-2026-28465 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-28465?

CVE-2026-28465 affects the following packages: @openclaw/voice-call (npm), @clawdbot/voice-call (npm). Ecosystems affected: npm.

How do I fix CVE-2026-28465?

Update @openclaw/voice-call to 2026.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-28465 is resolved across your whole dependency graph.

How do I detect CVE-2026-28465 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openclaw/voice-call, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-28465 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-28465?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-28465 can be triaged on real exposure rather than presence alone.

Is CVE-2026-28465 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-28465 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-28465?

CVE-2026-28465 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-28465?

CVE-2026-28465 is classified as CWE-290 (CWE-290). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-28465 published, and has it been updated?

CVE-2026-28465 was published on March 5, 2026 and was last updated on September 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-28465 — @openclaw/voice-call

Fix: openclaw/openclaw@a749db9

CVE-2026-28465 is a CWE-290 vulnerability in @openclaw/voice-call. A fix is available for @openclaw/voice-call — see the affected versions and patch details below.

OpenClaw voice-call < 2026.2.3 - Webhook Verification Bypass via Forwarded Headers

Also known asGHSA-3m3q-x3gj-f79x

Published

Mar 5, 2026

Updated

Sep 19, 2026

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-28465.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@openclaw/voice-callnpm

3Kdownloads / week

@clawdbot/voice-callnpm

14downloads / week

Description

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.

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@openclaw/voice-call`	all versions	2026.2.3`npm install @openclaw/voice-call@2026.2.3`
📦npm	`@clawdbot/voice-call`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openclaw/voice-call, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @openclaw/voice-call to 2026.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-28465 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-28465 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2026-28465. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## 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

O3 Security · Impact-Aware SCA

Is CVE-2026-28465 in your dependencies?

O3 Security finds CVE-2026-28465 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works