Openclaw\/voice-call
3 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Openclaw\/voice-call, a product in the ai ml space. Use it to gauge the current risk picture and drill into individual advisories.
Openclaw\/voice-call CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 3 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 0 |
Severity
How the 3 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High1
- Medium1
Latest CVEs
The 3 most recently published vulnerabilities affecting Openclaw\/voice-call.
- CVE-2026-32062OpenClaw 2026.2.21-2 < 2026.2.22 - Unauthenticated WebSocket Resource Exhaustion via Media Stream7.5
- CVE-2026-28465OpenClaw voice-call < 2026.2.3 - Webhook Verification Bypass via Forwarded Headers5.9
- GHSA-mfg5-7q5g-f37jOpenClaw voice-call media stream validated streams after upgrade, which could allow pre-start unauthenticated sockets to increase resource pressure—
Product grouping is registry-driven, with AI assist and human review. How it works