NetSight

Security Dashboard

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

Reset
1,088 matching advisories · page 8 of 37Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-rvfw-v7c7-3496 Malicious code in quickcolors (PyPI)Malware pip · quickcolors 2026-07-21 critical GHSA-f9cq-qmfc-wj2w Malicious code in qtcolor (PyPI)Malware pip · qtcolor, pip · qtcolor, pip · qtcolor 2026-07-21 critical GHSA-2rj8-242h-547w Malicious code in python2color (PyPI)Malware pip · python2color 2026-07-21 critical GHSA-6g7f-c5h3-47h5 Malicious code in pythoncoloringspkgv2 (PyPI)Malware pip · pythoncoloringspkgv2, pip · pythoncoloringspkgv2 2026-07-21 critical GHSA-qg55-r45v-ffvf Malicious code in pythoncoloringkitv2 (PyPI)Malware pip · pythoncoloringkitv2, pip · pythoncoloringkitv2 2026-07-21 critical GHSA-8jfh-7576-6fjc Malicious code in pythoncoloring (PyPI)Malware pip · pythoncoloring 2026-07-21 critical GHSA-vmhj-pfwp-cgrr Malicious code in pythoncoloringslibv2 (PyPI)Malware pip · pythoncoloringslibv2, pip · pythoncoloringslibv2 2026-07-21 critical GHSA-q9hw-rmpm-6xwr Malicious code in pythoncolorv4 (PyPI)Malware pip · pythoncolorv4 2026-07-21 critical GHSA-jggv-8chw-vj93 Malicious code in pythoncolorlibv1 (PyPI)Malware pip · pythoncolorlibv1 2026-07-21 critical GHSA-j7gm-p4m3-4jgq Malicious code in pythoncoloraddonv2 (PyPI)Malware pip · pythoncoloraddonv2, pip · pythoncoloraddonv2 2026-07-21 critical GHSA-8pmm-f32h-mh69 Malicious code in pythoncoloringv1 (PyPI)Malware pip · pythoncoloringv1 2026-07-21 critical GHSA-rxq8-2qxg-q84v Malicious code in pyqcolored (PyPI)Malware pip · pyqcolored, pip · pyqcolored 2026-07-21 critical GHSA-9x44-6cc7-vqhh Malicious code in pyqtcolor (PyPI)Malware pip · pyqtcolor, pip · pyqtcolor, pip · pyqtcolor +4 2026-07-21 critical GHSA-vcrp-jj5f-29hm Malicious code in pymulticolor (PyPI)Malware pip · pymulticolor 2026-07-21 critical GHSA-jj4p-458v-p29r Malicious code in pycolorv3 (PyPI)Malware pip · pycolorv3 2026-07-21 critical GHSA-h4h9-9xj9-4mv6 Malicious code in pycolorings (PyPI)Malware pip · pycolorings 2026-07-21 critical GHSA-mwrx-q8hq-frx8 Malicious code in pycolorstrex (PyPI)Malware pip · pycolorstrex 2026-07-21 critical GHSA-w8x5-9rg6-59rr Malicious code in pycolorio (PyPI)Malware pip · pycolorio, pip · pycolorio 2026-07-21 critical GHSA-3458-f5wf-fvp9 Malicious code in pycoloring (PyPI)Malware pip · pycoloring 2026-07-21 critical GHSA-ggr4-9hw7-crwj Malicious code in pycolorlibaryv1 (PyPI)Malware pip · pycolorlibaryv1 2026-07-21 critical GHSA-q3jc-m2j5-374h Malicious code in pycoloringv9 (PyPI)Malware pip · pycoloringv9 2026-07-21 critical GHSA-wvm5-78vx-x75c Malicious code in pycolorlib3 (PyPI)Malware pip · pycolorlib3, pip · pycolorlib3 2026-07-21 critical GHSA-338x-8ch9-fw2v Malicious code in pycoloringpkgsv2 (PyPI)Malware pip · pycoloringpkgsv2 2026-07-21 critical GHSA-j8p3-5398-p296 Malicious code in pycolorom (PyPI)Malware pip · pycolorom 2026-07-21 critical GHSA-vwwm-vmjj-3qxm Malicious code in pycoloramade (PyPI)Malware pip · pycoloramade, pip · pycoloramade, pip · pycoloramade +3 2026-07-21 critical GHSA-3x6j-65h8-4p6p Malicious code in pycolorate (PyPI)Malware pip · pycolorate, pip · pycolorate 2026-07-21 critical GHSA-9prc-465f-xgx5 Malicious code in pycolorz (PyPI)Malware pip · pycolorz, pip · pycolorz, pip · pycolorz +5 2026-07-21 critical GHSA-29q5-gxx6-8x6c Malicious code in pycolorlib001 (PyPI)Malware pip · pycolorlib001 2026-07-21 critical GHSA-h4j7-2pp4-2cp6 Malicious code in pycolorlib (PyPI)Malware pip · pycolorlib 2026-07-21 critical GHSA-vcxf-m3v3-3mjg Malicious code in pycolorating (PyPI)Malware pip · pycolorating 2026-07-21

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.