NetSight

Security Dashboard

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

Reset
65 matching advisories · page 1 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-fx7q-v4vh-68x3 Malicious code in dowload_ebok_ragdoll_dein_letzter_tag_by_daniel_cole_hbs5n (npm)Malware npm · dowload_ebok_ragdoll_dein_letzter_tag_by_daniel_cole_hbs5n 8 days ago critical GHSA-p37h-jfhx-8hpp Malicious code in keresztes (npm)Malware npm · keresztes 2026-09-17 critical GHSA-5wh2-j94m-rwpf Malware in dilxztechMalware npm · dilxztech 2026-09-14 critical GHSA-h4q4-78p6-g4h9 Malicious code in lium-io-gztensor (PyPI)Malware pip · lium-io-gztensor, pip · lium-io-gztensor, pip · lium-io-gztensor 2026-07-21 critical GHSA-4fq7-27j6-35mx Malicious code in gztensor-cli (PyPI)Malware pip · gztensor-cli, pip · gztensor-cli, pip · gztensor-cli +3 2026-07-21 critical GHSA-vfp8-q6q8-jfpp Malicious code in zztestownedtmp1 (RubyGems)Malware rubygems · zztestownedtmp1 2026-07-18 critical GHSA-j57m-7m27-xm6j Malicious code in zztest17785553774 (RubyGems)Malware rubygems · zztest17785553774 2026-07-18 critical GHSA-p6jp-c54v-c5v9 Malicious code in zztest17785553733 (RubyGems)Malware rubygems · zztest17785553733 2026-07-18 critical GHSA-gfv4-8524-cgrq Malicious code in zztest1778552006 (RubyGems)Malware rubygems · zztest1778552006 2026-07-18 critical GHSA-4ffg-jq89-wwp4 Malicious code in zztest17785553661 (RubyGems)Malware rubygems · zztest17785553661 2026-07-18 critical GHSA-gh79-cg62-9ppj Malicious code in zztest17785553805 (RubyGems)Malware rubygems · zztest17785553805 2026-07-18 critical GHSA-fw62-grch-39vp Malicious code in zztestno33 (RubyGems)Malware rubygems · zztestno33 2026-07-18 critical GHSA-x6f2-ghhj-6qpc Malicious code in zztest4098 (RubyGems)Malware rubygems · zztest4098 2026-07-18 critical GHSA-973q-jr2q-hvfp Malicious code in zztestno44 (RubyGems)Malware rubygems · zztestno44 2026-07-18 critical GHSA-68q2-xv64-m8x5 Malicious code in zztestproxyfooabcxyz (RubyGems)Malware rubygems · zztestproxyfooabcxyz 2026-07-18 critical GHSA-q25r-w62f-p284 Malicious code in zztest17785553702 (RubyGems)Malware rubygems · zztest17785553702 2026-07-18 critical GHSA-ph7w-w6mw-pxvx Malicious code in zztemp-ssf-2605 (RubyGems)Malware rubygems · zztemp-ssf-2605 2026-07-18 critical GHSA-prh4-xhwv-mwjm Malicious code in ztestmeta001 (RubyGems)Malware rubygems · ztestmeta001 2026-07-18 critical GHSA-gq2x-c7gv-v96j Malicious code in ztestlamb01 (RubyGems)Malware rubygems · ztestlamb01 2026-07-18 critical GHSA-8vcf-6qf4-pgc7 Malicious code in xabczztest (RubyGems)Malware rubygems · xabczztest 2026-07-18 critical GHSA-vhrr-679q-cfpp Malicious code in oaiztestxyz123 (RubyGems)Malware rubygems · oaiztestxyz123 2026-07-18 critical9.8 CVE-2025-46581 ZTE's ZXCDN product is affected by a Struts remote code execution (RCE) vulnerability. 2025-10-14 critical GHSA-rv2q-w6pf-w3xm Malware in zztest82Malware npm · zztest82 2025-03-04 critical GHSA-6952-mf6w-ph2g Malware in zztest890Malware npm · zztest890 2025-03-04 critical9.8 CVE-2024-10119 The wireless router WRTM326 from SECOM does not properly validate a specific parameter. zte · wrtm326_firmware 2024-10-18 critical9.8 CVE-2024-45415 The HTTPD binary in multiple ZTE routers has a stack-based buffer overflow vulnerability in check_data_integrity function. 2024-09-16 critical9.8 CVE-2024-45414 The HTTPD binary in multiple ZTE routers has a stack-based buffer overflow vulnerability in webPrivateDecrypt function. 2024-09-16 critical9.8 CVE-2022-45599 Aztech WMB250AC Mesh Routers Firmware Version 016 2020 is vulnerable to PHP Type Juggling in file /var/www/login.php, allows attackers to gain escalated privil… aztech · wmb250ac_firmware 2023-02-22 critical9.8 CVE-2022-39073 There is a command injection vulnerability in ZTE MF286R, Due to insufficient validation of the input parameters, an attacker could use the vulnerability to ex… zte · mf286r_firmware 2023-01-06 critical9.8 CVE-2022-39070 There is an access control vulnerability in some ZTE PON OLT products. zte · zxa10_c350m_firmware, zte · zxa10_c300m_firmware 2022-11-22

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.