CVE-2026-17512

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 week
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: None knownExposed: 0

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

A vulnerability has been found in ggml-org whisper.cpp 1.8.4-58. This impacts the function log_mel_spectrogram of the file src/whisper.cpp. The manipulation leads to out-of-bounds read. The attack needs to be performed locally. The pull request to fix this issue awaits acceptance.

CVSS v3
3.3
EG Score
3.3(medium)
EG Risk
19(Track)
EG Risk 19/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%
Exploitation0% × 40%
Automatability30% × 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-17512(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.1+dfsg1-1 (14 versions)——

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 43× 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-08-28 21:41 UTCEPSS rescore
  2. 2026-08-27 21:02 UTCEG score recompute
  3. 2026-08-27 21:02 UTCGHSA enrichment
  4. 2026-08-27 14:25 UTCEPSS rescore
  5. 2026-08-26 14:46 UTCEPSS rescore
  6. 2026-08-25 13:48 UTCEPSS rescore
  7. 2026-08-24 21:48 UTCEG score recompute
  8. 2026-08-24 21:48 UTCGHSA enrichment
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 02:32 UTCEG score recompute
  11. 2026-08-22 02:32 UTCGHSA enrichment
  12. 2026-08-20 22:55 UTCEPSS rescore
  13. 2026-08-19 07:16 UTCEG score recompute
  14. 2026-08-19 07:16 UTCGHSA enrichment
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 11:58 UTCEG score recompute
  19. 2026-08-16 11:58 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 01:30 UTCEPSS rescore
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 16:43 UTCEG score recompute
  24. 2026-08-13 16:43 UTCGHSA enrichment
  25. 2026-08-12 13:50 UTCEPSS rescore
Show 26 more
  1. 2026-08-11 13:42 UTCEPSS rescore
  2. 2026-08-11 00:00 UTCEPSS rescore
  3. 2026-08-10 21:02 UTCEG score recompute
  4. 2026-08-10 21:02 UTCGHSA enrichment
  5. 2026-08-09 13:46 UTCEPSS rescore
  6. 2026-08-08 16:37 UTCEPSS rescore
  7. 2026-08-08 01:47 UTCEG score recompute
  8. 2026-08-08 01:47 UTCGHSA enrichment
  9. 2026-08-06 13:46 UTCEPSS rescore
  10. 2026-08-05 19:17 UTCEPSS rescore
  11. 2026-08-05 06:32 UTCEG score recompute
  12. 2026-08-05 06:32 UTCGHSA enrichment
  13. 2026-08-04 15:10 UTCEPSS rescore
  14. 2026-08-03 10:35 UTCEPSS rescore
  15. 2026-08-02 11:13 UTCEG score recompute
  16. 2026-08-02 11:13 UTCGHSA enrichment
  17. 2026-08-02 02:26 UTCEPSS rescore
  18. 2026-08-01 04:15 UTCEPSS rescore
  19. 2026-07-30 15:57 UTCEG score recompute
  20. 2026-07-30 15:57 UTCGHSA enrichment
  21. 2026-07-27 20:42 UTCEG score recompute
  22. 2026-07-27 20:41 UTCGHSA enrichment
  23. 2026-07-27 13:24 UTCEG score recompute
  24. 2026-07-27 13:23 UTCNVD updateCVSS v4 → 1.9
  25. 2026-07-27 12:37 UTCEG score recompute
  26. 2026-07-27 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-17512?
CVE-2026-17512 is a low vulnerability published on July 27, 2026. A vulnerability has been found in ggml-org whisper.cpp 1.8.4-58. This impacts the function logmelspectrogram of the file src/whisper.cpp. The manipulation leads to out-of-bounds read. The attack needs to be performed locally. The pull request to fix this issue awaits acceptance.
When was CVE-2026-17512 disclosed?
CVE-2026-17512 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-17512 actively exploited?
CVE-2026-17512 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-17512?
CVE-2026-17512 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-17512?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17512, 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-17512

Explore →

Is Your Infrastructure Affected by CVE-2026-17512?

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

Start Free Scan →Browse All CVEs