CVE-2026-123748

chenyme grok2api WebSocket Proxy voice_ws_handler.go proxyVoiceWebSocket resource consumption

publishedCWE-400CWE-404

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.

Technical severity5.3 mediumCVSS 4.0 · CNA: VulDB

Published2026-11-06Source updated 2026-11-09

Collected2026-11-103 attributed sources

Fixes and workarounds

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: CNA: VulDB

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: CNA: VulDB

Fix

The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches.

Source: CNA: VulDB

Affected products and versions

Affected products, source version ranges and reporting authorities
Product	Versions	Authority
grok2api chenyme	3.1.0 (affected) 3.1.1 (affected) 3.1.2 (affected) 3.1.3 (affected) 3.1.4 (affected) 3.1.5 (affected) 3.1.6 (affected) 3.1.7 (unaffected)	CNA: VulDB

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / score	Vector	Authority
4.0 / 5.3 medium	`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`	CNA: VulDB
3.1 / 4.3 medium	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:X/RL:O/RC:C`	CNA: VulDB
3.0 / 4.3 medium	`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L/E:X/RL:O/RC:C`	CNA: VulDB
2.0 / 4.0 medium	`AV:N/AC:L/Au:S/C:N/I:N/A:P/E:ND/RL:OF/RC:C`	CNA: VulDB
4.0 / 5.3 medium	`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/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`	NVD: [email protected]
3.1 / 4.3 medium	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`	NVD: [email protected]
2.0 / 4.0 medium	`AV:N/AC:L/Au:S/C:N/I:N/A:P`	NVD: [email protected]

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

https://vuldb.com/vuln/431905CNA: VulDB · vdb-entry, technical-description
https://vuldb.com/vuln/431905/ctiCNA: VulDB · signature, permissions-required
https://vuldb.com/cve/CVE-2026-123748CNA: VulDB · third-party-advisory
https://vuldb.com/submit/1033605CNA: VulDB · third-party-advisory
https://github.com/chenyme/grok2api/issues/1071CNA: VulDB · issue-tracking
https://github.com/chenyme/grok2api/pull/1073CNA: VulDB · issue-tracking, patch
https://github.com/chenyme/grok2api/commit/7ad0f791f0a9eb5a0ddfe38ac4dfcef01e19a6d4CNA: VulDB · patch
https://github.com/chenyme/grok2api/releases/tag/v3.1.7CNA: VulDB · patch
https://github.com/chenyme/grok2api/CNA: VulDB · product
https://github.com/chenyme/grok2api/[email protected]
https://github.com/chenyme/grok2api/commit/7ad0f791f0a9eb5a0ddfe38ac4dfcef01e19a6d4[email protected]
https://github.com/chenyme/grok2api/issues/1071[email protected]
https://github.com/chenyme/grok2api/pull/1073[email protected]
https://github.com/chenyme/grok2api/releases/tag/v3.1.7[email protected]
https://vuldb.com/cve/CVE-2026-123748[email protected]
https://vuldb.com/submit/1033605[email protected]
https://vuldb.com/vuln/431905[email protected]
https://vuldb.com/vuln/431905/cti[email protected]

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Get an API key Use x402 Connect an agent

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide