# CVE-2025-14369: CVE-2025-14369

> An integer overflow in dr_flac allows attackers to cause denial of service via crafted FLAC files, affecting applications using this library.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Jan 2026
- **Updated:** 20 Jan 2026
- **Also known as:** DEBIAN-CVE-2025-14369, GHSA-3c35-prjf-p48q, MGASA-2026-0169, UBUNTU-CVE-2025-14369

## What is CVE-2025-14369?

CVE-2025-14369 is a medium-severity vulnerability in mackron dr_flac, published on 20 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

dr_flac, an audio decoder within the dr_libs toolset, contains an integer overflow vulnerability flaw due to trusting the totalPCMFrameCount field from FLAC metadata before calculating buffer size, allowing an attacker with a specially crafted file to perform DoS against programs using the tool.

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


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

Apply the vendor's patch.

## Is CVE-2025-14369 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14369 is a medium-severity vulnerability in mackron dr_flac, published on 20 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-14369 in the wild and no public exploit code.

Affected product: mackron dr_flac. 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-14369/ (Markdown: https://insights.sbomify.com/CVE-2025-14369/index.md)
```

## Sources

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

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