Cyber Resilience

CVE-2025-26305

Libming 0.4.8

Public PoC
Published
20 February 2025
Modified
22 April 2025
Patch / advisory
CVSS Score v3.1 8.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS Score 0.0038 31th percentile
Risk Priority 61 floored blend · peak EPSS

Summary

CVE-2025-26305 is a high-severity Heap Inspection (CWE-244) vulnerability in Libming Libming. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-26305 is a memory leak vulnerability in the parseSWF_SOUNDINFO function within util/parser.c of libming version 0.4.8. This issue affects the libming library, which handles parsing of Macromedia Flash (SWF) files, and is classified under CWE-244 (Improper Clearing of Heap Memory Before Release). The vulnerability was published on 2025-02-20 and carries a CVSS v3.1 base score of 8.2 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N), highlighting its high severity due to network accessibility and low attack complexity.

Remote attackers require no privileges or user interaction to exploit this flaw by supplying a specially crafted SWF file to a vulnerable libming instance. Successful exploitation triggers the memory leak, enabling a denial of service through resource exhaustion, while the high confidentiality impact indicates potential leakage of sensitive information from heap memory and low integrity impact from possible memory corruption.

Mitigation details and further discussion are available in the GitHub issue at https://github.com/libming/libming/issues/322.

EU & UK References

Vulnerability Data

A memory leak has been identified in the parseSWF_SOUNDINFO function in util/parser.c of libming v0.4.8, which allows attackers to cause a denial of service via a crafted SWF file.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-26304Same product: Libming Libming
CVE-2025-26309Same product: Libming Libming
CVE-2025-29497Same product: Libming Libming
CVE-2025-29488Same product: Libming Libming
CVE-2025-29486Same product: Libming Libming
CVE-2025-29489Same product: Libming Libming
CVE-2025-26310Same product: Libming Libming
CVE-2023-36239Same product: Libming Libming
CVE-2025-26311Same product: Libming Libming
CVE-2024-24148Same product: Libming Libming

Affected Assets

libming
libming
0.4.8

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-4 requires mechanisms that stop unintended transfer of sensitive data through shared resources such as heap memory reused after realloc.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-10 mostly match
prevents

Explicit example of removing confidential data from process memory directly prevents heap inspection exposure.

PR.PS-06 partial match
prevents

Secure SDLC practices encompass proper sensitive-memory handling but fixing this single CWE does not achieve the control.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Explicitly requires secure deletion of sensitive data, directly addressing improper heap clearing.

prevents

Secure SDLC processes can incorporate memory-safety requirements but do not specifically mandate heap clearing.

prevents

Mandates secure coding practices that include proper memory sanitization before release.

none

Secure architecture principles may reduce exposure but do not prescribe explicit heap-clearing techniques.

References