NetSight

Security Dashboard

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

Reset
1,323 matching advisories · page 5 of 45Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-frjh-9436-8269 Malicious code in apple-jira (npm)Malware npm · apple-jira 2026-09-02 critical GHSA-jhm3-rgwv-869q Malicious code in apple-date-hhyd (npm)Malware npm · apple-date-hhyd 2026-09-02 critical GHSA-rggm-cc93-g2xr Malicious code in apple-carrot-fzlq (npm)Malware npm · apple-carrot-fzlq 2026-09-02 critical GHSA-p954-8cgw-h7m2 Malicious code in apple-analytics (npm)Malware npm · apple-analytics 2026-09-02 critical GHSA-cq8p-j65f-wrmq Malicious code in apple-internal (npm)Malware npm · apple-internal 2026-09-02 critical GHSA-5f54-7633-79c6 Malicious code in apple-fig-pkxm (npm)Malware npm · apple-fig-pkxm 2026-09-02 critical GHSA-6584-x854-8h77 Malicious code in apple-e4v-project (npm)Malware npm · apple-e4v-project 2026-09-02 critical GHSA-pgr2-88fq-8q8v Malicious code in apple-date-quince-qnivq (npm)Malware npm · apple-date-quince-qnivq 2026-09-02 critical GHSA-26hm-9x5q-gw85 Malicious code in apple-checkout (npm)Malware npm · apple-checkout 2026-09-02 critical GHSA-prcm-3cxw-q987 Malicious code in apple-admin (npm)Malware npm · apple-admin 2026-09-02 critical GHSA-fggv-c94m-32f6 Malicious code in apple-bravo-pfsh (npm)Malware npm · apple-bravo-pfsh 2026-09-02 critical GHSA-43c9-5c49-2m6m Malicious code in apple-k27-project (npm)Malware npm · apple-k27-project 2026-09-02 critical GHSA-gjf6-xqg3-6hjp Malicious code in apple-gateway (npm)Malware npm · apple-gateway 2026-09-02 critical GHSA-vcqx-xgrc-6rqg Malicious code in apple-fig-india-uecxa (npm)Malware npm · apple-fig-india-uecxa 2026-09-02 critical GHSA-5gj7-7fg7-jv5p Malicious code in apple-delta-ohyg (npm)Malware npm · apple-delta-ohyg 2026-09-02 critical GHSA-x5q2-553f-v262 Malicious code in apple-event (npm)Malware npm · apple-event 2026-09-02 critical9.1 CVE-2026-82454 The Omnivore API (packages/api) before the fix in commit abf53d6 contains an authentication bypass in Apple sign-in token verification. 2026-08-29 critical9.8 CVE-2026-43798 A single crafted SSH message gives an unauthenticated network attacker an out-of-bounds stack write of attacker-controlled length and content against any appli… apple · swiftnio_ssh 2026-08-20 critical9.8 CVE-2026-65400 Apple macOS Improper Authentication VulnerabilityExploited Apple · macOS, apple · macos 2026-08-06 critical GHSA-wvr3-h93m-grxg Malicious code in react-native-paysafe-apple-pay (npm)Malware npm · react-native-paysafe-apple-pay 2026-07-27 critical GHSA-pf6f-8w3x-745h Malicious code in apple-mycelium-internal-research (npm)Malware npm · apple-mycelium-internal-research 2026-07-27 critical GHSA-7825-hjw2-qc37 Malicious code in @microsop/apple-mycelium-integrity-check (npm)Malware npm · @microsop/apple-mycelium-integrity-check 2026-07-27 critical9.8 CVE-2026-64775 A memory initialization issue was addressed with improved memory handling. apple · ipados, apple · iphone_os, apple · macos +3 2026-07-27 critical9.8 CVE-2026-64774 An integer overflow was addressed with improved input validation. apple · ipados, apple · iphone_os, apple · macos +2 2026-07-27 critical9.8 CVE-2026-64772 An out-of-bounds write issue was addressed with improved input validation. apple · ipados, apple · iphone_os, apple · macos +2 2026-07-27 critical9.8 CVE-2026-64771 A buffer overflow was addressed with improved bounds checking. apple · ipados, apple · iphone_os, apple · macos +2 2026-07-27 critical9.8 CVE-2026-64770 An out-of-bounds write issue was addressed with improved bounds checking. apple · ipados, apple · iphone_os, apple · macos +2 2026-07-27 critical9.8 CVE-2026-64769 An out-of-bounds write issue was addressed with improved bounds checking. apple · ipados, apple · iphone_os, apple · macos +2 2026-07-27 critical9.8 CVE-2026-64767 A buffer overflow was addressed with improved bounds checking. apple · macos 2026-07-27 critical9.8 CVE-2026-64762 An out-of-bounds read was addressed with improved bounds checking. apple · macos 2026-07-27

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.