CVE-2025-52194

Exp

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.

Published: 2025-08-21 Last update: 2025-09-11 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-52194 is rated High Exploit Risk (64.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.32%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-52194

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-52194

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-29 0.25% 0.32% +0.08%
2 2026-05-27 0.32% 0.25% -0.08%
3 2026-05-22 — 0.32% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-52194

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-52194

OS Trackers for CVE-2025-52194

vendor priority summary link
alpine — CVE-2025-52194: 1 source package rows (libsndfile); 42 state rows across 6 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 0, open 42. https://security.alpinelinux.org/vuln/CVE-2025-52194
redhat medium — https://access.redhat.com/security/cve/CVE-2025-52194
suse high — https://www.suse.com/security/cve/CVE-2025-52194/
ubuntu medium CVE-2025-52194 medium priority: Ubuntu including 1 source packages (libsndfile), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): deferred 7, ignored 1, needs-triage 1. https://ubuntu.com/security/CVE-2025-52194

Affected software / configurations for CVE-2025-52194

Vendor Product Version Raw CPE
libsndfile_project libsndfile <= 1.2.2 cpe:2.3:a:libsndfile_project:libsndfile:*:*:*:*:*:*:*:*

References for CVE-2025-52194

cvelogic Threat Intelligence