NetSight

Security Dashboard

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

Reset
4,501 matching advisories · page 1 of 151Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.4 CVE-2026-113968 A logic issue was addressed with improved state management. This issue is fixed in iOS 18.7.12... Apple · iOS and iPadOS, Apple · macOS, Apple · visionOS +3 12 days ago medium5.4 CVE-2026-113965 This issue was addressed with improved checks. This issue is fixed in iOS 18.7.12 and iPadOS 18.7... Apple · iOS and iPadOS, Apple · macOS, Apple · visionOS +3 12 days ago medium5.4 CVE-2026-113964 A logic issue was addressed with improved state management. This issue is fixed in iOS 18.7.12... Apple · iOS and iPadOS, Apple · macOS, Apple · visionOS +3 12 days ago medium6.5 CVE-2026-113960 This issue was addressed by removing the vulnerable code. This issue is fixed in iOS 26.7.3 and... Apple · iOS and iPadOS, Apple · macOS, Apple · visionOS +2 12 days ago medium5.5 CVE-2026-113963 An authorization issue was addressed with improved state management. This issue is fixed in iOS... Apple · iOS and iPadOS, Apple · visionOS, Apple · watchOS +2 12 days ago medium5.6 CVE-2026-113957 An attacker who controls the registry, a mirror, or the network path to it may be able to serve arbitrary image content in response to a pull by digest, so tha… Apple · Containerization, Apple · Container 24 days ago medium5.9 CVE-2026-86983 A remote attacker may be able to terminate a process that passes attacker-controlled input to the P-384 VOPRF API without bounding its length. Apple · swift-crypto 24 days ago medium5.1 CVE-2026-86990 An access issue was addressed with improved access restrictions. apple · ipados, apple · iphone_os, apple · macos +1 26 days ago medium5.5 CVE-2026-86987 An authorization issue was addressed with improved entitlement checks. apple · ipados, apple · iphone_os 26 days ago medium6.5 CVE-2026-86973 An out-of-bounds read was addressed with improved bounds checking. apple · safari, apple · ipados, apple · iphone_os +1 26 days ago medium6.5 CVE-2026-86971 An out-of-bounds write issue was addressed with improved bounds checking. apple · ipados, apple · iphone_os, apple · macos +1 26 days ago medium6.5 CVE-2026-86954 An out-of-bounds read was addressed with improved bounds checking. apple · ipados, apple · iphone_os, apple · macos +3 26 days ago medium5.5 CVE-2026-86942 An out-of-bounds read was addressed with improved bounds checking. apple · ipados, apple · iphone_os, apple · macos +1 26 days ago medium5.5 CVE-2026-86925 An authorization issue was addressed with improved state management. apple · iphone_os, apple · ipados, apple · macos +1 26 days ago medium5.5 CVE-2026-86920 An authorization issue was addressed with improved state management. apple · iphone_os, apple · ipados, apple · macos +1 26 days ago medium6.2 CVE-2026-86877 A path traversal issue was addressed with improved path validation. apple · macos 26 days ago medium5.5 CVE-2026-84610 A file quarantine bypass was addressed with additional checks. apple · macos 26 days ago medium6.5 CVE-2026-84590 An out-of-bounds write issue was addressed with improved bounds checking. apple · macos 26 days ago medium5.5 CVE-2026-84542 An access issue was addressed with improved access restrictions. apple · macos 26 days ago medium5.5 CVE-2026-84498 The issue was addressed with improved memory handling. apple · macos 26 days ago medium6.5 CVE-2026-84496 An out-of-bounds write issue was addressed with improved bounds checking. apple · macos 26 days ago medium4.4 CVE-2026-84493 An authentication issue was addressed with improved state management. This issue is fixed in iOS... apple · ipados, apple · iphone_os 26 days ago medium5.5 CVE-2026-65397 An authorization issue was addressed with improved state management. apple · ipados, apple · iphone_os, apple · macos +1 26 days ago medium5.5 CVE-2026-64789 This issue was addressed with improved validation of file attributes. apple · macos 26 days ago medium5.5 CVE-2026-64750 An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in... apple · ipados, apple · iphone_os, apple · macos 26 days ago medium5.5 CVE-2026-43736 An authorization issue was addressed with improved state management. apple · macos 26 days ago medium5.4 CVE-2026-113952 A logic issue was addressed with improved checks. This issue is fixed in Safari 27.2, iOS 26.7.2... apple · safari, apple · ipados, apple · iphone_os +1 26 days ago medium5.5 CVE-2026-113948 A permissions issue was addressed with additional restrictions. This issue is fixed in macOS... apple · macos 26 days ago medium6.5 CVE-2026-113943 An out-of-bounds write issue was addressed with improved bounds checking. apple · macos 26 days ago medium5.5 CVE-2026-113940 An out-of-bounds read was addressed with improved bounds checking. This issue is fixed in macOS... apple · macos 26 days ago

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.