NetSight

Security Dashboard

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

Reset
651 matching advisories · page 2 of 22Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.1 CVE-2026-56597 HCL BigFix Service Management is affected by a Sensitive Information Leakage vulnerability, which could allow an unauthenticated attacker to extract internal I… hcltech · bigfix_service_management 2026-09-18 low3.1 CVE-2026-56595 HCL BigFix Service Management is affected by a CORS Misconfiguration vulnerability due to improperly validated origin headers, which could allow an attacker to… hcltech · bigfix_service_management 2026-09-18 medium6.5 CVE-2026-56592 HCL BigFix Service Management is affected by an Improper Authentication validation vulnerability related to inadequate account lockouts, which could allow an u… hcltech · bigfix_service_management 2026-09-18 medium6.4 CVE-2026-56590 HCL BigFix Service Management is affected by an Unrestricted File Upload vulnerability due to improper file validation controls, which could allow an unauthent… hcltech · bigfix_service_management 2026-09-18 medium5.0 CVE-2026-21848 HCL BigFix Service Management is affected by a Security Misconfiguration vulnerability, which could allow an authenticated attacker to exploit improper access … hcltech · bigfix_service_management 2026-09-18 high7.6 CVE-2026-67103 HCL BigFix Service Management is affected by Cross-Site Scripting (XSS) vulnerability, which could allow an attacker to inject unsanitized malicious scripts th… hcltech · bigfix_service_management 2026-09-18 high8.1 CVE-2026-67102 HCL BigFix Service Management is affected by a high-severity Broken Access Control vulnerability, which could allow a low-privileged user to gain unauthorized … hcltech · bigfix_service_management 2026-09-18 critical9.3 CVE-2026-67101 HCL BigFix Service Management is affected by a Server-Side Request Forgery (SSRF) vulnerability in its search functionality, which could allow an attacker to f… hcltech · bigfix_service_management 2026-09-18 critical9.8 CVE-2026-67100 HCL BigFix Service Management is affected by SQL Injection flaw and a Cross-Tenant Data Exposure flaw vulnerabilities. hcltech · bigfix_service_management 2026-09-18 critical GHSA-xgvj-w2p3-pq6v Malicious code in liquid_lungfish_z3n (npm)Malware npm · liquid_lungfish_z3n 2026-09-17 critical GHSA-59cf-5gpj-wp5m Malicious code in liobc-ug-agfiag (npm)Malware npm · liobc-ug-agfiag 2026-09-17 critical GHSA-cp84-vch3-46vm Malicious code in linguistic_lungfish-smiletea (npm)Malware npm · linguistic_lungfish-smiletea 2026-09-17 critical GHSA-6wf4-4p58-3wr3 Malicious code in likely_lungfish_z3n (npm)Malware npm · likely_lungfish_z3n 2026-09-17 critical GHSA-7x2m-86gc-pjrc Malicious code in like_lungfish_z3n (npm)Malware npm · like_lungfish_z3n 2026-09-17 critical GHSA-24xr-3wrg-mr4c Malicious code in level_lungfish_z3n (npm)Malware npm · level_lungfish_z3n 2026-09-17 critical GHSA-v6rg-4vvg-4hgf Malicious code in lengthy_lungfish_z3n (npm)Malware npm · lengthy_lungfish_z3n 2026-09-17 critical GHSA-2gj6-mrm6-m5jc Malicious code in legislative_kingfisher_z3n (npm)Malware npm · legislative_kingfisher_z3n 2026-09-17 critical GHSA-vhwv-9j6w-gxqr Malicious code in leading_kingfisher_z3n (npm)Malware npm · leading_kingfisher_z3n 2026-09-17 critical GHSA-m9rv-v7vp-pqhr Malicious code in large-coffee-kingfisher (npm)Malware npm · large-coffee-kingfisher 2026-09-17 critical GHSA-pmqw-247v-986v Malicious code in keen_flyingfish_z3n (npm)Malware npm · keen_flyingfish_z3n 2026-09-17 critical GHSA-jrgg-fmh8-cqg3 Malicious code in kapvino-sovni-sgfi (npm)Malware npm · kapvino-sovni-sgfi 2026-09-17 critical GHSA-qpcp-9wvq-pw6r Malicious code in kapvino-sovni-gfi (npm)Malware npm · kapvino-sovni-gfi 2026-09-17 critical GHSA-8q93-3fg9-98h9 Malicious code in kapvino-sovni-fffsgfi (npm)Malware npm · kapvino-sovni-fffsgfi 2026-09-17 critical GHSA-qgxf-6h5h-57pg Malicious code in kapvino-sovni-fsgfi (npm)Malware npm · kapvino-sovni-fsgfi 2026-09-17 critical GHSA-747c-3p97-wx9m Malicious code in kapvino-sovni-ffsgfi (npm)Malware npm · kapvino-sovni-ffsgfi 2026-09-17 critical GHSA-9qmh-xwj7-xrx4 Malicious code in kapvino-sovni-fafkfsgfi (npm)Malware npm · kapvino-sovni-fafkfsgfi 2026-09-17 critical GHSA-c5wp-xv8p-4qfw Malicious code in kapvino-sovni-fafskfskfsgfi (npm)Malware npm · kapvino-sovni-fafskfskfsgfi 2026-09-17 critical GHSA-h262-cf8m-xqf3 Malicious code in kapvino-sovni-fafskfsgfi (npm)Malware npm · kapvino-sovni-fafskfsgfi 2026-09-17 critical GHSA-pgf8-c4g7-3722 Malicious code in kapvino-sovni-fafsfskfsgfi (npm)Malware npm · kapvino-sovni-fafsfskfsgfi 2026-09-17 critical GHSA-pw3p-jmj4-7m45 Malicious code in kapvino-sovni-fafgskfskfsgfi (npm)Malware npm · kapvino-sovni-fafgskfskfsgfi 2026-09-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.