# CVE-2026-92751: CMAK through 3.0.0.6 Cross-Site Request Forgery via Missing CSRF Filter

> Attackers can perform destructive actions like topic deletion on behalf of authenticated CMAK operators due to missing CSRF protection.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-f8jr-q32f-87q5

## What is CVE-2026-92751?

CVE-2026-92751 is a high-severity vulnerability in yahoo CMAK, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

CMAK through 3.0.0.6 fails to install a cross-site request forgery filter, allowing attackers to perform state-changing actions on behalf of authenticated operators. Attackers can craft hidden forms that submit to destructive endpoints like topic deletion and cluster configuration changes, leveraging the operator's HTTP Basic authentication credentials or play-basic-authentication cookie without SameSite protection.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-92751 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92751 is a high-severity vulnerability in yahoo CMAK, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92751 exists.

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

## Sources

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

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