# CVE-2026-92778: CMAK through 3.0.0.6 Feature Gate Bypass via HTML Form Routes

> Attackers can bypass feature gates to disrupt leadership in managed Kafka clusters by accessing unprotected HTML form routes.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-8c8p-h27x-rrc9

## What is CVE-2026-92778?

CVE-2026-92778 is a medium-severity vulnerability in yahoo CMAK, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

CMAK through 3.0.0.6 fails to apply the scheduled leader election feature toggle to HTML form routes, allowing attackers to bypass the feature gate. Attackers can access the form endpoints to start and stop the recurring election scheduler, disrupting leadership across managed Kafka clusters.

Weakness: CWE-693 (Protection Mechanism Failure)

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


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

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

## Is CVE-2026-92778 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92778 is a medium-severity vulnerability in yahoo CMAK, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92778 in the wild and no public exploit code.

Affected product: yahoo CMAK. 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-92778/ (Markdown: https://insights.sbomify.com/CVE-2026-92778/index.md)
```

## Sources

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

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