cve.bz

CVE-2025-56226 libsndfile project libsndfile

5.3 mediumExploit referenceEPSS 0.4%

Medium (5.3) in libsndfile project libsndfile. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

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

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-01-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-401 Missing Release of Memory after Effective Lifetime
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-56226 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-56226?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-56226?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-56226 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
libsndfile_project:libsndfilefrom 1.1.0 through 1.2.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12libsndfileno fix listedDEBIAN-CVE-2025-56226
Debian13libsndfile1.2.2-2+deb13u1DEBIAN-CVE-2025-56226
Debian14libsndfile1.2.2-4DEBIAN-CVE-2025-56226
Ubuntu20.04:LTS, 24.04:LTS, 25.10 and 4 morelibsndfileno fix listedUBUNTU-CVE-2025-56226
openSUSETumbleweedlibsndfile1.2.2-4.1openSUSE-SU-2026:10061-1
Azure Linux3libsndfile1.2.2-4AZL-74855

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

To exploit this flaw, an attacker needs to be able to process a malicious MP3 file with an application linked to the libsndfile library. Also, the only security impact of this issue is a high consumption of system memory that eventually can cause an application crash and result in a denial of service, there is no memory corruption or arbitrary code execution. Due to these reasons, this vulnerability has been rated with a moderate severity.

Red Hat's mitigation

Do not process untrusted MP3 files with the libsndfile library.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10libsndfileFix deferred
Red Hat Enterprise Linux 6libsndfileOut of support scope
Red Hat Enterprise Linux 7libsndfileNot affected
Red Hat Enterprise Linux 8libsndfileNot affected
Red Hat Enterprise Linux 9libsndfileNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-56226.

References

Check your stackJSON