# CVE-2026-123788: chenyme grok2api STT Billing voice_ws_handler.go behavioral workflow


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-279p-xx78-79p3

## What is CVE-2026-123788?

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

### Official description

A security vulnerability has been detected in chenyme grok2api up to 3.1.6. The impacted element is an unknown function of the file backend/internal/transport/http/inference/voice_ws_handler.go of the component STT Billing. The manipulation leads to enforcement of behavioral workflow. The attack may be initiated remotely. Upgrading to version 3.1.7 is sufficient to resolve this issue. The identifier of the patch is 7ad0f791f0a9eb5a0ddfe38ac4dfcef01e19a6d4. Upgrading the affected component is recommended.

Weakness: CWE-841 (Improper Enforcement of Behavioral Workflow), CWE-840

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


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

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

## Is CVE-2026-123788 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123788 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123788 is a medium-severity vulnerability in chenyme grok2api, published on 6 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123788 exists.

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-123788/ (Markdown: https://insights.sbomify.com/CVE-2026-123788/index.md)
```

## Sources

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

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