NetSight

Security Dashboard

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

Reset
30 matching advisories · page 1 of 1Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-q7gh-hf5c-wm2g Malicious code in msgpackrpc (PyPI)Malware pip · msgpackrpc 17 days ago critical GHSA-q3pj-88g8-46rf Malware in fatfingers-mybigpackageMalware npm · fatfingers-mybigpackage 2026-08-14 critical GHSA-xvcf-q9q3-xhg7 Malware in @keyv/serialize-msgpackrMalware npm · @keyv/serialize-msgpackr 2026-08-04 critical GHSA-49h2-vq5m-22hf Malware in pullingpackageeeeMalware npm · pullingpackageeee 2026-07-30 critical GHSA-275r-557m-9c6w Malware in pullingpackageeeeeeeeeeMalware npm · pullingpackageeeeeeeeee 2026-07-30 critical GHSA-vf7m-5f8w-gw69 Malware in pullingpackagedMalware npm · pullingpackaged 2026-07-30 critical GHSA-hvqj-6qw4-pfrf Malware in pullingpackageeeeeeeeMalware npm · pullingpackageeeeeeee 2026-07-30 critical GHSA-wm5v-jh9g-w34v Malware in pullingpackageeeeeeeeeeeMalware npm · pullingpackageeeeeeeeeee 2026-07-30 critical GHSA-wrw3-chmv-4qvc Malware in pullingpackageeeeeeeeeMalware npm · pullingpackageeeeeeeee 2026-07-30 critical GHSA-m86j-3g6g-q7r7 Malware in pullingpackageeeMalware npm · pullingpackageee 2026-07-30 critical GHSA-hq8m-wmq9-632v Malware in pullingpackageeeeeeeMalware npm · pullingpackageeeeeee 2026-07-30 critical GHSA-x98q-m69m-vp6m Malware in pullingpackageeMalware npm · pullingpackagee 2026-07-30 critical GHSA-f2gr-qgm3-wg22 Malware in pullingpackageMalware npm · pullingpackage 2026-07-30 critical GHSA-ch7p-4j2g-f2f7 Malicious code in activerecord-msgpack-serializer (RubyGems)Malware rubygems · activerecord-msgpack-serializer 2026-07-18 critical9.8 CVE-2023-46427 An issue was discovered in gpac version 2.3-DEV-rev588-g7edc40fee-master, allows remote attackers to execute arbitrary code, cause a denial of service (DoS), a… gpac · gpac 2024-03-09 critical9.1 CVE-2024-0322 Out-of-bounds Read in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2024-01-08 critical9.8 CVE-2024-0321 Stack-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2024-01-08 critical9.8 CVE-2023-46932 Heap Buffer Overflow vulnerability in GPAC version 2.3-DEV-rev617-g671976fcc-master, allows attackers to execute arbitrary code and cause a denial of service (… gpac · gpac 2023-12-09 critical9.8 CVE-2023-46347 In the module "Step by Step products Pack" (ndk_steppingpack) version 1.5.6 and before from NDK Design for PrestaShop, a guest can perform SQL injection. ndkdesign · ndk_steppingpack 2023-10-25 critical9.8 CVE-2023-2840 NULL Pointer Dereference in GitHub repository gpac/gpac prior to 2.2.2. gpac · gpac 2023-05-22 critical9.1 CVE-2023-2838 Out-of-bounds Read in GitHub repository gpac/gpac prior to 2.2.2. gpac · gpac 2023-05-22 critical9.8 CVE-2022-36190 GPAC mp4box 2.1-DEV-revUNKNOWN-master has a use-after-free vulnerability in function gf_isom_dovi_config_get. gpac · gpac 2022-08-17 critical9.8 CVE-2022-1795 Use After Free in GitHub repository gpac/gpac prior to v2.1.0-DEV. gpac · gpac 2022-05-18 critical9.1 CVE-2020-19751 An issue was discovered in gpac 0.8.0. gpac · gpac 2021-09-07 critical9.8 CVE-2021-23410 Deserialization of Untrusted Data in msgpack npm · msgpack 2021-07-21 critical9.8 CVE-2021-28300 NULL Pointer Dereference in the "isomedia/track.c" module's "MergeTrack()" function of GPAC v0.5.2 allows attackers to execute arbitrary code or cause a Denial… gpac · gpac 2021-04-14 critical9.8 CVE-2020-11558 An issue was discovered in libgpac.a in GPAC 0.8.0, as demonstrated by MP4Box. gpac · gpac 2020-04-05 critical9.8 CVE-2018-13006 An issue was discovered in MP4Box in GPAC 0.7.1. debian · debian_linux, gpac · gpac, canonical · ubuntu_linux 2018-06-29 critical9.8 CVE-2018-13005 An issue was discovered in MP4Box in GPAC 0.7.1. debian · debian_linux, gpac · gpac, canonical · ubuntu_linux 2018-06-29 critical9.8 CVE-2018-11218 Memory Corruption was discovered in the cmsgpack library in the Lua subsystem in Redis before 3.2.12, 4.x before 4.0.10, and 5.x before 5.0 RC2 because of stac… redislabs · redis, debian · debian_linux, oracle · communications_operations_monitor +1 2018-06-17

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.