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.
CVE-2026-17513
Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-07-27. a secondary CVSS source baseline 3.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.3
- EG Score
- 3.3(high)
- EG Risk
- 31(Track)EG Risk 31/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity33% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 27, 2026
Last Modified
July 27, 2026
References (7)
- cna@vuldbhttps://github.com/ggml-org/whisper.cpp/
- cna@vuldbhttps://github.com/ggml-org/whisper.cpp/issues/3924
- cna@vuldbhttps://vuldb.com/cve/CVE-2026-17513
- cna@vuldbhttps://vuldb.com/submit/799055
- cna@vuldbhttps://vuldb.com/vuln/383383
- cna@vuldbhttps://vuldb.com/vuln/383383/cti
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/ggml-org/whisper.cpp/
Vendor Advisories for CVE-2026-17513(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 20:39 UTCGHSA enrichment
- 2026-07-27 17:20 UTCEG score recompute
- 2026-07-27 17:20 UTCGHSA enrichment
- 2026-07-27 17:18 UTCNVD updateCVSS v4 → 1.9
- 2026-07-27 17:02 UTCEG score recompute
- 2026-07-27 17:02 UTCGHSA enrichment
- 2026-07-27 17:00 UTCMITRE cvelistV5CVSS v4 → 4.8
- 2026-07-27 14:59 UTCEG score recompute
- 2026-07-27 14:18 UTCNVD updateCVSS v4 → 1.9
- 2026-07-27 13:37 UTCEG score recompute
- 2026-07-27 13:35 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-17513?
When was CVE-2026-17513 disclosed?
What is the CVSS score of CVE-2026-17513?
How do I remediate CVE-2026-17513?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-17513
Is Your Infrastructure Affected by CVE-2026-17513?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.