NetSight

Security Dashboard

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

Reset
169 matching advisories · page 3 of 6Index updated 7 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-prcf-65p6-fhwm Malicious code in algol-weywot-loopback-nodejs (npm)Malware npm · algol-weywot-loopback-nodejs 2026-08-31 critical GHSA-875r-8wf9-658h Malicious code in algol-sagitta-nodejs-ursa (npm)Malware npm · algol-sagitta-nodejs-ursa 2026-08-31 critical GHSA-9vr5-4rwm-crmm Malicious code in algol-aldebaran-cressida-nodejs (npm)Malware npm · algol-aldebaran-cressida-nodejs 2026-08-31 critical GHSA-m6v9-8jcm-pwgx Malicious code in aether-cygnus-nodejs-got (npm)Malware npm · aether-cygnus-nodejs-got 2026-08-31 critical GHSA-wvv3-2xq3-p429 Malicious code in acamar-child-process-oauth-nodejs (npm)Malware npm · acamar-child-process-oauth-nodejs 2026-08-31 critical GHSA-9vg7-pm72-4598 Malicious code in @zalastax/nolb-nodejst (npm)Malware npm · @zalastax/nolb-nodejst 2026-08-14 critical GHSA-46w8-g867-mrq4 Malicious code in @zalastax/nolb-nodejsp (npm)Malware npm · @zalastax/nolb-nodejsp 2026-08-14 critical GHSA-5jc5-c7c9-4php Malicious code in @zalastax/nolb-nodejs_ (npm)Malware npm · @zalastax/nolb-nodejs_ 2026-08-14 critical GHSA-5h65-fq46-wr3h Malicious code in @zalastax/nolb-nodejsn (npm)Malware npm · @zalastax/nolb-nodejsn 2026-08-14 critical GHSA-chm3-7gvg-gm9c Malicious code in @zalastax/nolb-nodejsr (npm)Malware npm · @zalastax/nolb-nodejsr 2026-08-14 critical GHSA-rmvh-2hcq-cxm2 Malicious code in @zalastax/nolb-nodejsa (npm)Malware npm · @zalastax/nolb-nodejsa 2026-08-14 critical GHSA-hv5g-q24v-6f79 Malicious code in @zalastax/nolb-nodejsw (npm)Malware npm · @zalastax/nolb-nodejsw 2026-08-14 critical GHSA-7gwg-w46g-wm99 Malicious code in functions-framework-nodejs (npm)Malware npm · functions-framework-nodejs 2026-08-13 critical GHSA-8cx5-gjvj-8q8v Malicious code in @amiga-fwk-nodejs/log (npm)Malware npm · @amiga-fwk-nodejs/log 2026-07-26 critical GHSA-g8h2-q3c5-hcm7 Malicious code in @amiga-fwk-nodejs/metrics (npm)Malware npm · @amiga-fwk-nodejs/metrics 2026-07-26 critical GHSA-whqv-q5hv-396f Malicious code in 8888acc-utility-service-nodejs-clien (npm)Malware npm · 8888acc-utility-service-nodejs-clien 2026-07-26 critical9.8 CVE-2026-48930 A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings. nodejs · node.js 2026-06-26 critical9.4 CVE-2026-46399 HAX CMS helps manage microsite universe with PHP or NodeJs backends. 2026-06-05 critical9.3 CVE-2026-46396 Stored XSS via <iframe> in HAX CMS allows access to sensitive client-side data and account takeover npm · @haxtheweb/haxcms-nodejs, npm · @haxtheweb/video-player, npm · @haxtheweb/iframe-loader 2026-05-19 critical9.3 CVE-2026-46395 HAX CMS helps manage microsite universe with PHP or NodeJs backends. npm · @haxtheweb/haxcms-nodejs 2026-05-19 critical9.3 CVE-2026-46496 HAX CMS: Stored XSS via '<video-player>' component allows arbitrary JavaScript execution and token theft npm · @haxtheweb/haxcms-nodejs, npm · @haxtheweb/video-player 2026-05-19 critical9.8 CVE-2026-33228 Prototype Pollution via parse() in NodeJS flatted npm · flatted 2026-03-19 critical GHSA-jpvg-2xxh-xxvh Malware in aws-crt-nodejsMalware npm · aws-crt-nodejs 2026-01-21 critical10.0 CVE-2026-21636 A flaw in Node.js's permission model allows Unix Domain Socket (UDS) connections to bypass network restrictions when `--permission` is enabled. nodejs · node.js 2026-01-20 critical9.1 CVE-2025-55130 A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relative symlink paths. nodejs · node.js 2026-01-20 critical GHSA-5xww-jhm3-vmv3 Malware in @asyncapi/nodejs-templateMalware npm · @asyncapi/nodejs-template, npm · @asyncapi/nodejs-template 2025-11-24 critical GHSA-4w37-25mh-3jcc Malware in @asyncapi/nodejs-ws-templateMalware npm · @asyncapi/nodejs-ws-template, npm · @asyncapi/nodejs-ws-template 2025-11-24 critical GHSA-jp96-hc4j-6xx2 Malware in zohocrm-nodejs-sdk-3.0Malware npm · zohocrm-nodejs-sdk-3.0 2025-10-29 critical GHSA-mqvf-rmj2-mp9q Malware in nodejs-backpackMalware npm · nodejs-backpack 2025-07-24 critical9.8 CVE-2025-54127 NodeJS version of HAX CMS Has Insecure Default Configuration That Leads to Unauthenticated Access npm · @haxtheweb/haxcms-nodejs 2025-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.