NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
84 matching advisories · page 1 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2026-95125 libming through 0.4.8 contains a heap buffer overflow in r_readc() in src/blocks/fromswf.c. libming 44 days ago medium6.5 CVE-2025-29497 libming v0.4.8 was discovered to contain a memory leak via the parseSWF_MORPHFILLSTYLES function. libming · libming 2025-03-27 medium6.5 CVE-2025-29496 libming v0.4.8 was discovered to contain a segmentation fault via the decompileDUPLICATECLIP function. libming · libming 2025-03-27 medium6.5 CVE-2025-29494 libming v0.4.8 was discovered to contain a segmentation fault via the decompileGETMEMBER function. libming · libming 2025-03-27 medium6.5 CVE-2025-29493 libming v0.4.8 was discovered to contain a segmentation fault via the decompileGETPROPERTY function. libming · libming 2025-03-27 medium6.5 CVE-2025-29492 libming v0.4.8 was discovered to contain a segmentation fault via the decompileSETVARIABLE function. libming · libming 2025-03-27 medium6.5 CVE-2025-29491 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… libming · libming 2025-03-27 medium6.5 CVE-2025-29490 libming v0.4.8 was discovered to contain a segmentation fault via the decompileCALLMETHOD function. libming · libming 2025-03-27 medium6.5 CVE-2025-29489 libming v0.4.8 was discovered to contain a memory leak via the parseSWF_MORPHLINESTYLES function. libming · libming 2025-03-27 medium6.5 CVE-2025-29488 libming v0.4.8 was discovered to contain a memory leak via the parseSWF_INITACTION function. libming · libming 2025-03-27 medium6.5 CVE-2025-29486 libming v0.4.8 was discovered to contain a memory leak via the parseSWF_PLACEOBJECT3 function. libming · libming 2025-03-27 medium6.5 CVE-2025-29485 libming v0.4.8 was discovered to contain a segmentation fault via the decompileRETURN function. libming · libming 2025-03-27 medium6.5 CVE-2025-29483 libming v0.4.8 was discovered to contain a memory leak via the parseSWF_ENABLEDEBUGGER2 function. libming · libming 2025-03-27 medium6.5 CVE-2025-26311 Multiple memory leaks have been identified in the clip actions parsing functions (parseSWF_CLIPACTIONS and parseSWF_CLIPACTIONRECORD) in util/parser.c of libmi… libming · libming 2025-02-20 medium6.5 CVE-2025-26310 Multiple memory leaks have been identified in the ABC file parsing functions (parseABC_CONSTANT_POOL and `parseABC_FILE) in util/parser.c of libming v0.4.8, wh… libming · libming 2025-02-20 medium6.5 CVE-2025-26309 A memory leak has been identified in the parseSWF_DEFINESCENEANDFRAMEDATA function in util/parser.c of libming v0.4.8, which allows attackers to cause a denial… libming · libming 2025-02-20 medium6.5 CVE-2025-26308 A memory leak has been identified in the parseSWF_FILTERLIST function in util/parser.c of libming v0.4.8, which allows attackers to cause a denial of service v… libming · libming 2025-02-20 medium6.5 CVE-2025-26307 A memory leak has been identified in the parseSWF_IMPORTASSETS2 function in util/parser.c of libming v0.4.8, which allows attackers to cause a denial of servic… libming · libming 2025-02-20 medium6.5 CVE-2025-26306 A memory leak has been identified in the readSizedString function in util/read.c of libming v0.4.8, which allows attackers to cause a denial of service via a c… libming · libming 2025-02-20 medium6.5 CVE-2024-24150 A memory leak issue discovered in parseSWF_TEXTRECORD in libming v0.4.8 allows attackers to cause a denial of service via a crafted SWF file. libming · libming 2024-02-29 medium6.5 CVE-2024-24149 A memory leak issue discovered in parseSWF_GLYPHENTRY in libming v0.4.8 allows attackers to cause a denial of service via a crafted SWF file. libming · libming 2024-02-29 medium6.5 CVE-2024-24147 A memory leak issue discovered in parseSWF_FILLSTYLEARRAY in libming v0.4.8 allows attackers to cause s denial of service via a crafted SWF file. libming · libming 2024-02-29 medium6.5 CVE-2024-24146 A memory leak issue discovered in parseSWF_DEFINEBUTTON in libming v0.4.8 allows attackers to cause s denial of service via a crafted SWF file. libming · libming 2024-02-29 medium4.3 CVE-2024-25770 libming 0.4.8 contains a memory leak vulnerability in /libming/src/actioncompiler/listaction.c. libming · libming 2024-02-26 medium6.5 CVE-2023-40781 Buffer Overflow vulnerability in Libming Libming v.0.4.8 allows a remote attacker to cause a denial of service via a crafted .swf file to the makeswf function. libming · libming 2023-08-28 medium5.5 CVE-2023-30085 Buffer Overflow vulnerability found in Libming swftophp v.0.4.8 allows a local attacker to cause a denial of service via the cws2fws function in util/decompile… libming · libming 2023-05-09 medium5.5 CVE-2023-30084 An issue found in libming swftophp v.0.4.8 allows a local attacker to cause a denial of service via the stackVal function in util/decompile.c. libming · libming 2023-05-09 medium5.5 CVE-2023-30083 Buffer Overflow vulnerability found in Libming swftophp v.0.4.8 allows a local attacker to cause a denial of service via the newVar_N in util/decompile.c. libming · libming 2023-05-09 medium6.5 CVE-2021-34342 Ming 0.4.8 has an out-of-bounds read vulnerability in the function newVar_N() in decompile.c which causes a huge information leak. libming · ming, fedoraproject · fedora 2022-03-10 medium6.5 CVE-2021-34341 Ming 0.4.8 has an out-of-bounds read vulnerability in the function decompileIF() in the decompile.c file that causes a direct segmentation fault and leads to d… libming · ming, fedoraproject · fedora 2022-03-10

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.