Quick answers
- Is CVE-2026-17512 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17512 being exploited in the wild.
- How severe is CVE-2026-17512?
- Low severity, with a CVSS score of 3.3, published 27 July 2026.
- Which products and versions are affected?
- Ggml-Org Whisper.Cpp 1.8.4-58.
- Is there a fix for CVE-2026-17512?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-17512 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-17512?
- Check whether you run Ggml-Org Whisper.Cpp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An out-of-bounds read vulnerability exists in whisper.cpp version 1.8.4-58 within the log_mel_spectrogram function in src/whisper.cpp. The issue stems from the use of std::reverse_copy to apply reflective padding to the start of an audio signal. The function attempts to copy a fixed number of samples (stage_2_pad, typically 200) regardless of the actual input length. If a user provides an audio buffer with fewer than 201 samples, the source range for the copy operation extends beyond the allocated heap buffer. This can be triggered via any API path that accepts user-supplied audio, such as whisper_full(). A pull request (#3925) has been submitted to reject inputs that are too short for the required padding.
Affected products
- ggml-org whisper.cpp 1.8.4-58
Timeline
- 2026-07-03: disclosed: Issue reported on GitHub repository
- 2026-07-04: other: Pull request submitted to fix the issue
- 2026-07-27: advisory: CVE published and NVD record created