CVE-2026-17513

LOWPre-NVD 3.33.3—
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.3
EG Score
3.3(medium)
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 computed
Severity33% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 27, 2026

Last Modified

July 27, 2026

References (7)

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.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
whisper.cpp1.7.6+dfsg-1 ... 1.9.3+dfsg-1~exp1 (17 versions)——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-17 01:47 UTCEG score recompute
  3. 2026-09-17 01:47 UTCGHSA enrichment
  4. 2026-09-16 14:07 UTCEPSS rescore
  5. 2026-09-16 05:14 UTCEPSS rescore
  6. 2026-09-13 21:13 UTCEG score recompute
  7. 2026-09-13 21:13 UTCGHSA enrichment
  8. 2026-09-12 15:00 UTCEPSS rescore
  9. 2026-09-11 14:52 UTCEPSS rescore
  10. 2026-09-11 09:36 UTCEPSS rescore
  11. 2026-09-10 22:35 UTCEG score recompute
  12. 2026-09-10 22:35 UTCGHSA enrichment
  13. 2026-09-10 09:34 UTCEPSS rescore
  14. 2026-09-08 22:00 UTCEPSS rescore
  15. 2026-09-08 02:11 UTCEG score recompute
  16. 2026-09-08 02:11 UTCGHSA enrichment
  17. 2026-09-07 16:01 UTCEPSS rescore
  18. 2026-09-06 13:47 UTCEPSS rescore
  19. 2026-09-05 05:47 UTCEG score recompute
  20. 2026-09-05 05:47 UTCGHSA enrichment
  21. 2026-09-01 23:00 UTCEG score recompute
  22. 2026-09-01 23:00 UTCGHSA enrichment
  23. 2026-09-01 13:53 UTCEPSS rescore
  24. 2026-09-01 04:39 UTCEPSS rescore
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 57 more
  1. 2026-08-29 23:55 UTCEG score recompute
  2. 2026-08-29 23:55 UTCGHSA enrichment
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-26 14:46 UTCEPSS rescore
  6. 2026-08-25 08:49 UTCEG score recompute
  7. 2026-08-25 08:49 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 12:25 UTCEG score recompute
  10. 2026-08-22 12:25 UTCGHSA enrichment
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-20 22:55 UTCEPSS rescore
  13. 2026-08-19 17:03 UTCEPSS rescore
  14. 2026-08-19 16:00 UTCEG score recompute
  15. 2026-08-19 16:00 UTCGHSA enrichment
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-16 19:30 UTCEG score recompute
  19. 2026-08-16 19:30 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-13 23:05 UTCEG score recompute
  24. 2026-08-13 23:05 UTCGHSA enrichment
  25. 2026-08-13 22:00 UTCEPSS rescore
  26. 2026-08-12 13:50 UTCEPSS rescore
  27. 2026-08-11 02:41 UTCEG score recompute
  28. 2026-08-11 02:41 UTCGHSA enrichment
  29. 2026-08-11 00:00 UTCEPSS rescore
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-08 16:37 UTCEPSS rescore
  32. 2026-08-08 06:17 UTCEG score recompute
  33. 2026-08-08 06:17 UTCGHSA enrichment
  34. 2026-08-06 13:46 UTCEPSS rescore
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-05 09:53 UTCEG score recompute
  37. 2026-08-05 09:53 UTCGHSA enrichment
  38. 2026-08-04 10:38 UTCEPSS rescore
  39. 2026-08-03 10:35 UTCEPSS rescore
  40. 2026-08-02 13:30 UTCEG score recompute
  41. 2026-08-02 13:30 UTCGHSA enrichment
  42. 2026-08-02 02:26 UTCEPSS rescore
  43. 2026-08-01 04:15 UTCEPSS rescore
  44. 2026-07-30 17:06 UTCEG score recompute
  45. 2026-07-30 17:05 UTCGHSA enrichment
  46. 2026-07-30 01:30 UTCEPSS rescore
  47. 2026-07-27 20:39 UTCGHSA enrichment
  48. 2026-07-27 17:20 UTCEG score recompute
  49. 2026-07-27 17:20 UTCGHSA enrichment
  50. 2026-07-27 17:18 UTCNVD updateCVSS v4 → 1.9
  51. 2026-07-27 17:02 UTCEG score recompute
  52. 2026-07-27 17:02 UTCGHSA enrichment
  53. 2026-07-27 17:00 UTCMITRE cvelistV5CVSS v4 → 4.8
  54. 2026-07-27 14:59 UTCEG score recompute
  55. 2026-07-27 14:18 UTCNVD updateCVSS v4 → 1.9
  56. 2026-07-27 13:37 UTCEG score recompute
  57. 2026-07-27 13:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-17513?
CVE-2026-17513 is a low vulnerability published on July 27, 2026. A vulnerability was found in ggml-org whisper.cpp 95ea8f9b. Affected is the function ggmlftypetoggmltype 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…
When was CVE-2026-17513 disclosed?
CVE-2026-17513 was first published in the National Vulnerability Database on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17513 actively exploited?
CVE-2026-17513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-17513?
CVE-2026-17513 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-17513?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17513, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-17513

Explore →

Is Your Infrastructure Affected by CVE-2026-17513?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs