CVE-2026-123788 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
grok2api is a proxy that exposes Grok models through an API, and its speech-to-text billing component has a flaw in its voice WebSocket handler. A remote attacker may be able to manipulate the billing workflow to bypass its enforcement.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams that self-host grok2api up to 3.1.6 and expose its speech-to-text voice endpoint to remote clients. Deployments that do not run the voice WebSocket feature or that use a managed service are less likely to be exposed; the sources do not say more.
Not affected if version-3.1.7-or-later
Who cares ai-proxy, grok2api, self-hosted, speech-to-text
3.1.6 are listed as affected.backend/internal/transport/http/inference/voice_ws_handler.go if you run a patched fork.3.1.7 (patch commit 7ad0f791f0a9eb5a0ddfe38ac4dfcef01e19a6d4).A security vulnerability has been detected in chenyme grok2api up to 3.1.6. The impacted element is an unknown function of the file backend/internal/transport/http/inference/voice_ws_handler.go of the component STT Billing. The manipulation leads to enforcement of behavioral workflow. The attack may be initiated remotely. Upgrading to version 3.1.7 is sufficient to resolve this issue. The identifier of the patch is 7ad0f791f0a9eb5a0ddfe38ac4dfcef01e19a6d4. Upgrading the affected component is recommended.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.