# CVE-2025-52194: Memory corruption in n/a

> A buffer overflow in libsndfile allows attackers to execute arbitrary code via malformed IRCAM audio files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Aug 2025
- **Updated:** 21 Aug 2025
- **Also known as:** AZL-66669, AZL-66671, CLSA-2026-1786483996, CLSA-2026-1786490187, GHSA-3w6g-vv96-4ph6, UBUNTU-CVE-2025-52194

## What is CVE-2025-52194?

CVE-2025-52194 is a high-severity memory corruption vulnerability in n/a, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A buffer overflow vulnerability exists in libsndfile version 1.2.2 and potentially earlier versions when processing malformed IRCAM audio files. The vulnerability occurs in the ircam_read_header function at src/ircam.c:164 during sample rate processing, leading to memory corruption and potential code execution.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Libsndfile Project Libsndfile.

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

Upgrade to a fixed version.

## Is CVE-2025-52194 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-6892](https://insights.sbomify.com/CVE-2017-6892/): Memory corruption in libsndfile (high 8.8)
- [CVE-2022-33064](https://insights.sbomify.com/CVE-2022-33064/): Memory corruption in n/a (high 7.8)
- [CVE-2022-33065](https://insights.sbomify.com/CVE-2022-33065/): Integer overflow in n/a (high 7.8)
- [CVE-2026-37555](https://insights.sbomify.com/CVE-2026-37555/): Integer overflow in n/a (high 7.5)
- [CVE-2024-50613](https://insights.sbomify.com/CVE-2024-50613/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52194 is a high-severity memory corruption vulnerability in n/a, published on 21 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52194 in the wild and no public exploit code.

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

## Sources

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

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