CVE-2025-56226

Exp

Libsndfile <=1.2.2 contains a memory leak vulnerability in the mpeg_l3_encoder_init() function within the mpeg_l3_encode.c file.

Published: 2026-01-14 Last update: 2026-01-21 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-56226 is rated Exploit Available (50/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.07%). 2 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-56226

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

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

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-02-25 0.04% 0.07% +0.02%
2 2026-01-22 0.05% 0.04% -0.01%
3 2026-01-20 — 0.05% —

Full EPSS history (4 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L 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:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 1.4 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-56226

OS Trackers for CVE-2025-56226

vendor priority summary link
alpine — CVE-2025-56226: 1 source package rows (libsndfile); 12 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 12. https://security.alpinelinux.org/vuln/CVE-2025-56226
debian unimportant CVE-2025-56226 unimportant priority: Debian including 1 source packages (libsndfile), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2025-56226
redhat medium — https://access.redhat.com/security/cve/CVE-2025-56226
suse medium CVE-2025-56226 severity moderate: SUSE including 7 source package names (libsndfile, libsndfile-devel, …), 59 product×package rows across 21 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS, … (21 product lines)): Known Not Affected 56, Fixed 3. https://www.suse.com/security/cve/CVE-2025-56226/
ubuntu low CVE-2025-56226 low priority: Ubuntu including 1 source packages (libsndfile), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): needs-triage 8, ignored 1. https://ubuntu.com/security/CVE-2025-56226

Affected software / configurations for CVE-2025-56226

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

References for CVE-2025-56226

cvelogic Threat Intelligence