# CVE-2026-17513: ggml-org whisper.cpp ggml.c ggml_ftype_to_ggml_type assertion

> A local attacker can trigger a reachable assertion in whisper.cpp, causing a denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-17513, GHSA-hqg6-4q5h-9ggc, UBUNTU-CVE-2026-17513

## What is CVE-2026-17513?

CVE-2026-17513 is a medium-severity denial of service vulnerability in ggml-org whisper.cpp, published on 27 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in ggml-org whisper.cpp 95ea8f9b. Affected is the function ggml_ftype_to_ggml_type of the file ggml/src/ggml.c. The manipulation of the argument ftype results in reachable assertion. The attack requires a local approach. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-617 (Reachable Assertion)

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


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

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

## Is CVE-2026-17513 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17513 is a medium-severity denial of service vulnerability in ggml-org whisper.cpp, published on 27 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-17513 exists.

Affected product: ggml-org whisper.cpp. 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-17513/ (Markdown: https://insights.sbomify.com/CVE-2026-17513/index.md)
```

## Sources

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

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