CVE-2026-124574chenyme grok2api incorrect privilege assignment
CVE-2026-124574 is a incorrect privilege assignment in chenyme grok2api, rated low (2.1 on CVSS 4.0).
Why this priority: Low severity, with no exploitation signal.
Published · Updated · NVD status: Deferred
What it is
A user or process is given privileges it should not have. The software does not check, or checks wrongly, whether a caller may do something.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker reach data or actions their role should not allow.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade chenyme grok2api to 3.1.7 or later.
- Until it is patched, review who holds accounts that can reach it.
Description from NVD
A vulnerability was determined in chenyme grok2api up to 3.1.6. This vulnerability affects the function beginSelectionSession of the file backend/internal/application/gateway/video.go of the component Video Job Retry Handler. This manipulation causes improper authorization. It is possible to initiate the attack remotely. The exploit has been publicly disclosed and may be utilized. Upgrading to version 3.1.7 is able to resolve this issue. Patch name: 199b3abecc14907176dae1f1cacf125419caa94d. It is suggested to upgrade the affected component.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Permission checks in APIs and admin surfaces. The flaw sits between one role or tenant and another.
- Multi-tenant services. The flaw sits between one role or tenant and another.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Between one role or tenant and another. An attacker who crosses it can reach data or actions their role should not allow.
Questions to answer about your own systems
- Where does chenyme grok2api run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Patches and commits
Advisories
Issue reports
More reading
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.