# CVE-2025-14569: ggml-org whisper.cpp common-whisper.cpp read_audio_data use after free

> A use-after-free vulnerability in whisper.cpp allows local attackers to potentially execute code or cause denial of service via crafted audio data.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2025
- **Updated:** 12 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-14569, GHSA-wjrw-m667-4g2c, UBUNTU-CVE-2025-14569

## What is CVE-2025-14569?

CVE-2025-14569 is a medium-severity use after free vulnerability in ggml-org whisper.cpp, published on 12 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was detected in ggml-org whisper.cpp up to 1.8.2. Affected is the function read_audio_data of the file /whisper.cpp/examples/common-whisper.cpp. The manipulation results in use after free. The attack requires a local approach. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-416 (Use After Free), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-14569?


## How do I fix CVE-2025-14569?

No fix has been published for CVE-2025-14569 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-14569 being exploited?

There is no known exploitation of CVE-2025-14569 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14569 and fix it if it is affected.

What it is: CVE-2025-14569 is a medium-severity use after free vulnerability in ggml-org whisper.cpp, published on 12 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14569 in the wild and no public exploit code.

Affected product: ggml-org whisper.cpp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14569/ (Markdown: https://insights.sbomify.com/CVE-2025-14569/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14569
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14569
- OSV: https://osv.dev/vulnerability/CVE-2025-14569

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14569/
Summaries are generated and may contain mistakes; the official description above is the record.