VulnerabilityPublished 6 Nov 2026

CVE-2026-123788: chenyme grok2api · Enforcement of Behavioral Workflow

Affects chenyme grok2apiSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.3 Medium · fixed in 3.1.7 : update chenyme grok2api when convenient.

Data as of 6 Nov 2026, 21:34 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulDB)	CVSS 4.0	5.3
CNA (VulDB)	CVSS 3.1	4.3
CNA (VulDB)	CVSS 3.0	4.3
CNA (VulDB)	CVSS 2.0	4.0

Patch: Available – fixed in 3.1.7

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 6 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
chenymegrok2api	Affected 3.1.0 – 3.1.6 7 affected builds	Fixed in–

CPE configurations (1)

cpe:2.3:a:chenyme:grok2api:*:*:*:*:*:*:*:*

AI-suggested

Upgrade chenyme grok2api to version 3.1.7 or later, which contains the official fix for this vulnerability. No additional mitigation steps are indicated.

Description

CVE-2026-123788 is a medium severity vulnerability in chenyme grok2api versions 3.1.0 through 3.1.6. It involves an issue in the STT Billing component's backend/internal/transport/http/inference/voice_ws_handler.go file, where manipulation can lead to enforcement of behavioral workflow. The vulnerability can be exploited remotely without user interaction. Upgrading to version 3.1.7 resolves the issue.

Impact

The vulnerability allows remote attackers to manipulate the behavioral workflow enforcement in the affected component, which may disrupt or alter the expected behavior of the speech-to-text billing process. There is no indication of privilege escalation, user interaction, or confidentiality/integrity/availability impact beyond workflow enforcement. No known exploits are reported in the wild.

Summary

This vulnerability affects chenyme grok2api up to version 3.1.6 in the STT Billing component, specifically in an unknown function within the voice_ws_handler.go file. The flaw allows remote attackers to enforce behavioral workflow, potentially impacting the application's intended operation. The vulnerability has a CVSS 4.0 base score of 5.3, indicating medium severity, with network attack vector, low attack complexity, and no privileges required. The issue is fixed in version 3.1.7, with the patch identified by commit 7ad0f791f0a9eb5a0ddfe38ac4dfcef01e19a6d4.

References

Community reviews

Loading reviews…