CVE-2026-17513

LOWPre-NVD 3.33.3
EchelonGraph scoreHIGH 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: ghsa, secondary
Trending — 4 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: 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(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 computed
Severity33% × 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

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.

  1. 2026-07-27 20:39 UTCGHSA enrichment
  2. 2026-07-27 17:20 UTCEG score recompute
  3. 2026-07-27 17:20 UTCGHSA enrichment
  4. 2026-07-27 17:18 UTCNVD updateCVSS v4 → 1.9
  5. 2026-07-27 17:02 UTCEG score recompute
  6. 2026-07-27 17:02 UTCGHSA enrichment
  7. 2026-07-27 17:00 UTCMITRE cvelistV5CVSS v4 → 4.8
  8. 2026-07-27 14:59 UTCEG score recompute
  9. 2026-07-27 14:18 UTCNVD updateCVSS v4 → 1.9
  10. 2026-07-27 13:37 UTCEG score recompute
  11. 2026-07-27 13:35 UTCMITRE cvelistV5first tracked

Frequently asked(4)

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.
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

Explore the affected products and dependency analysis for 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.