libming libming

Don't miss out!

Thousands of developers use stack.watch to stay informed.
Get an email whenever new security vulnerabilities are reported in any libming product.

RSS Feeds for libming security vulnerabilities

Create a CVE RSS feed including security vulnerabilities found in libming products with stack.watch. Just hit watch, then grab your custom RSS feed url.

Products by libming Sorted by Most Security Vulnerabilities since 2018

libming Ming90 vulnerabilities
Ming is a library for generating Macromedia Flash files (.swf), written in C

libming Ming7 vulnerabilities

By the Year

In 2026 there have been 0 vulnerabilities in libming. Last year, in 2025 libming had 22 security vulnerabilities published. Right now, libming is on track to have less security vulnerabilities in 2026 than it did last year.




Year Vulnerabilities Average Score
2026 0 0.00
2025 22 0.00
2024 6 6.50
2023 9 7.30
2022 7 6.50
2021 0 0.00
2020 4 0.00
2019 7 7.80
2018 42 6.71

It may take a day or so for new libming vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.

Recent libming Security Vulnerabilities

CVE Date Vulnerability Products
CVE-2025-29496 Mar 27, 2025
libming 0.4.8 segfault in decompileDUPLICATECLIP enables DoS libming v0.4.8 was discovered to contain a segmentation fault via the decompileDUPLICATECLIP function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted SWF file.
Ming
CVE-2025-29493 Mar 27, 2025
libming v0.4.8: DecompileGETPROPERTY SegFault DoS libming v0.4.8 was discovered to contain a segmentation fault via the decompileGETPROPERTY function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted SWF file.
Ming
CVE-2025-29488 Mar 27, 2025
Libming 0.4.8 Mem Leak via parseSWF_INITACTION libming v0.4.8 was discovered to contain a memory leak via the parseSWF_INITACTION function.
Ming
CVE-2025-29491 Mar 27, 2025
libming 0.48 DoS via parseSWF_DEFINEBINARYDATA allocation-size-too-big An allocation-size-too-big error in the parseSWF_DEFINEBINARYDATA function of libming v0.48 allows attackers to cause a Denial of Service (DoS) via supplying a crafted SWF file.
Ming
CVE-2025-29494 Mar 27, 2025
libming 0.4.8 DoS via decompileGETMEMBER segmentation fault libming v0.4.8 was discovered to contain a segmentation fault via the decompileGETMEMBER function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted SWF file.
Ming
CVE-2025-29489 Mar 27, 2025
Memory Leak in libming v0.4.8 via parseSWF_MORPHLINESTYLES libming v0.4.8 was discovered to contain a memory leak via the parseSWF_MORPHLINESTYLES function.
Ming
CVE-2025-29487 Mar 27, 2025
DoS via OOM in parseABC_STRING_INFO of libming 0.4.8 An out-of-memory error in the parseABC_STRING_INFO function of libming v0.4.8 allows attackers to cause a Denial of Service (DoS) due to allocator exhaustion.
Ming
CVE-2025-29497 Mar 27, 2025
libming v0.4.8 Mem Leak via parseSWF_MORPHFILLSTYLES libming v0.4.8 was discovered to contain a memory leak via the parseSWF_MORPHFILLSTYLES function.
Ming
CVE-2025-29490 Mar 27, 2025
libming 0.4.8 DoS via crafted SWF, segfault in decompileCALLMETHOD libming v0.4.8 was discovered to contain a segmentation fault via the decompileCALLMETHOD function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted SWF file.
Ming
CVE-2025-29492 Mar 27, 2025
Segfault in libming v0.4.8 decompileSETVARIABLE libming v0.4.8 was discovered to contain a segmentation fault via the decompileSETVARIABLE function.
Ming
Built by Foundeo Inc., with data from the National Vulnerability Database (NVD). Privacy Policy. Use of this site is governed by the Legal Terms
Disclaimer
CONTENT ON THIS WEBSITE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. Always check with your vendor for the most up to date, and accurate information.