CVE-2026-123748: A security flaw has been discovered in chenyme grok2api up to 3.1.6
CVE-2026-123748 is a medium-severity flaw (CVSS 4.3) affecting grok2api. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
A security flaw has been discovered in chenyme grok2api up to 3.1.6. Affected by this vulnerability is the function proxyVoiceWebSocket of the file backend/internal/transport/http/inference/voice_ws_handler.go of the component WebSocket Proxy. The manipulation results in resource consumption. The attack may be launched remotely. Upgrading to version 3.1.7 addresses this issue. The patch is identified as 7ad0f791f0a9eb5a0ddfe38ac4dfcef01e19a6d4. I
Why this priority
- No elevated risk signals yet
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-11-06 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-123748?
grok2api: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2026-123748 being exploited?
CVE-2026-123748 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-123748 affect?
CVE-2026-123748 affects grok2api. Severity is medium (CVSS 4.3). A security flaw has been discovered in chenyme grok2api up to 3.1.6. Affected by this vulnerability is the function proxyVoiceWebSocket of the file backend/internal/transport/http/inference/voice_ws_handler.go of the component WebSocket Pro
How urgent is CVE-2026-123748?
Priority 15/100. No elevated risk signals yet.