# CVE-2026-123748: chenyme grok2api WebSocket Proxy voice_ws_handler.go proxyVoiceWebSocket resource consumption


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-rv3x-8h48-5m2m

## What is CVE-2026-123748?

CVE-2026-123748 is a medium-severity vulnerability in chenyme grok2api, published on 6 Nov 2026. 

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

Weakness: CWE-404 (Improper Resource Shutdown or Release), CWE-400 (Uncontrolled Resource Consumption)

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


## How do I fix CVE-2026-123748?

No fix has been published for CVE-2026-123748 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-123748 being exploited?

There is no known exploitation of CVE-2026-123748 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123748 and fix it if it is affected.

What it is: CVE-2026-123748 is a medium-severity vulnerability in chenyme grok2api, published on 6 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123748 in the wild and no public exploit code.

Affected product: chenyme grok2api. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123748/ (Markdown: https://insights.sbomify.com/CVE-2026-123748/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123748
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123748
- OSV: https://osv.dev/vulnerability/CVE-2026-123748

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123748/
Summaries are generated and may contain mistakes; the official description above is the record.