NetSight

Security Dashboard

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

Reset
4,501 matching advisories · page 12 of 151Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2026-64714 A memory corruption issue was addressed with improved bounds checking. apple · ipados, apple · iphone_os, apple · macos +1 2026-09-14 medium5.5 CVE-2026-43808 A use-after-free issue was addressed with improved memory management. apple · ipados, apple · iphone_os, apple · macos +2 2026-09-14 medium6.5 CVE-2026-43791 A validation issue was addressed with improved input sanitization. apple · macos 2026-09-14 medium6.6 CVE-2026-43788 An integer overflow was addressed with improved input validation. apple · macos 2026-09-14 medium5.9 CVE-2026-43787 A logic issue was addressed with improved checks. apple · macos 2026-09-14 medium5.5 CVE-2026-43785 A permissions issue was addressed with additional restrictions. apple · ipados, apple · iphone_os, apple · macos +2 2026-09-14 medium5.5 CVE-2026-43762 The issue was addressed with improved checks. apple · ipados, apple · iphone_os, apple · macos +1 2026-09-14 medium6.5 CVE-2026-43761 An out-of-bounds write issue was addressed with improved bounds checking. apple · macos 2026-09-14 medium5.5 CVE-2026-43741 A logic issue was addressed with improved state management. apple · macos 2026-09-14 medium5.5 CVE-2026-43737 An authorization issue was addressed with improved validation. apple · ipados, apple · iphone_os, apple · macos +2 2026-09-14 medium6.5 CVE-2026-43719 A use-after-free issue was addressed with improved memory management. apple · macos 2026-09-14 medium5.3 CVE-2026-43696 An authorization issue was addressed with improved entitlement checks. apple · macos 2026-09-14 medium5.5 CVE-2026-43695 An authorization issue was addressed with improved state management. apple · ipados, apple · iphone_os, apple · macos +3 2026-09-14 medium4.7 CVE-2026-43690 A race condition was addressed with improved locking. apple · macos 2026-09-14 medium6.5 CVE-2026-43687 The issue was addressed with improved memory handling. apple · ipados, apple · iphone_os, apple · macos +3 2026-09-14 medium6.5 CVE-2026-43677 An out-of-bounds write issue was addressed by removing the vulnerable code. apple · macos 2026-09-14 medium4.6 CVE-2026-43674 An authentication issue was addressed with improved state management. apple · ipados, apple · iphone_os 2026-09-14 medium5.5 CVE-2026-43664 This issue was addressed with improved data protection. apple · ipados, apple · iphone_os, apple · macos +2 2026-09-14 medium5.5 CVE-2026-28968 An out-of-bounds write issue was addressed with improved bounds checking. apple · ipados, apple · iphone_os, apple · macos +3 2026-09-14 medium4.3 CVE-2026-28966 An out-of-bounds write issue was addressed with improved bounds checking. apple · ipados, apple · iphone_os, apple · macos +2 2026-09-14 medium5.5 CVE-2026-28937 This issue was addressed through improved state management. apple · macos 2026-09-14 medium6.5 CVE-2026-28934 A buffer overflow was addressed with improved bounds checking. apple · macos 2026-09-14 medium5.5 CVE-2026-28933 A use-after-free issue was addressed with improved memory management. apple · macos 2026-09-14 medium5.5 CVE-2026-28899 A logic issue was addressed with improved checks. apple · macos 2026-09-14 medium6.1 CVE-2026-28836 A correctness issue was addressed with improved checks. apple · macos 2026-09-14 medium5.5 CVE-2026-65367 A null pointer dereference was addressed with improved input validation. apple · ipados, apple · iphone_os 2026-08-25 medium5.5 CVE-2026-64705 A buffer overflow was addressed with improved bounds checking. apple · macos 2026-08-25 medium6.1 CVE-2026-65053 Horde IMP's AppleDouble MIME viewer writes an attacker-controlled attachment name into an HTML status block without escaping it. 2026-08-24 medium4.3 CVE-2026-20679 The issue was addressed with improved checks. apple · macos 2026-08-21 medium4.3 CVE-2026-64777 A malicious builder peer may be able to request an in-context file by name from the host and receive the contents of whatever the name resolves to, even when i… apple · container 2026-08-20

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.