NetSight

Security Dashboard

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

Reset
4,501 matching advisories · page 17 of 151Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2026-46371 Fleet: Observer-level enrollment secret extraction via ORDER BY oracle on Apple MDM commands endpoint go · github.com/fleetdm/fleet/v4 2026-06-12 medium5.3 CVE-2026-28898 swift-nio-http2's HTTP/2-to-HTTP/1.1 codec did not validate pseudo-header values for control characters before placing them into the translated HTTP/1.1 messag… swift · github.com/apple/swift-nio-http2 2026-06-12 medium6.9 CVE-2026-28975 NIOExtras: NIOHTTPRequestDecompressor ratio limit bypass via inflated Content-Length swift · github.com/apple/swift-nio-extras 2026-06-12 medium6.3 CVE-2026-28970 SwiftNIO: CRLF Injection in outbound HTTP request URI via NIOHTTPRequestHeadersValidator swift · github.com/apple/swift-nio 2026-06-12 medium5.5 CVE-2025-46313 A logging issue was addressed with improved data redaction. apple · macos 2026-06-11 medium5.3 CVE-2025-46308 An authorization issue was addressed with improved state management. apple · ipados, apple · iphone_os, apple · macos 2026-06-11 medium5.5 CVE-2025-46293 This issue was addressed with improved handling of symlinks. apple · macos 2026-06-11 medium5.5 CVE-2025-43339 An access issue was addressed with additional sandbox restrictions. apple · macos 2026-06-11 medium5.5 CVE-2025-43278 This issue was addressed with improved handling of symlinks. apple · macos 2026-06-11 medium5.5 CVE-2025-30459 A privacy issue was addressed by removing the vulnerable code. apple · macos 2026-06-11 medium5.5 CVE-2025-30431 The issue was addressed with improved checks. apple · macos 2026-06-11 medium5.5 CVE-2025-24268 A parsing issue in the handling of directory paths was addressed with improved path validation. apple · macos 2026-06-11 medium5.5 CVE-2025-24165 A permissions issue was addressed with additional restrictions. apple · macos 2026-06-11 medium5.5 CVE-2025-60485 A segmentation violation in the gf_isom_apple_set_tag_ex function (/isomedia/isom_write.c) of GPAC Project/MP4Box before 26.02.0 allows attackers to cause a De… GPAC Project/MP4Box 2026-06-01 medium5.5 CVE-2026-46202 In the Linux kernel, the following vulnerability has been resolved: HID: appletb-kbd: run inactivity autodim from workqueues The autodim code in hid-appletb-kb… linux · linux_kernel 2026-05-28 medium5.5 CVE-2025-46307 A logic issue was addressed with improved restrictions. apple · macos 2026-05-26 medium5.5 CVE-2025-46280 An out-of-bounds read was addressed with improved bounds checking. apple · macos 2026-05-26 medium5.5 CVE-2025-43451 A permissions issue was addressed by removing the vulnerable code. apple · macos 2026-05-26 medium5.5 CVE-2025-43290 A permissions issue was addressed with additional restrictions. apple · macos 2026-05-26 medium5.5 CVE-2025-43289 A logic issue was addressed with improved validation. apple · macos 2026-05-26 medium6.5 CVE-2026-20685 An attacker in a privileged network position may be able to leak sensitive information. apple · private_cloud_compute 2026-05-18 medium6.2 CVE-2026-43666 An out-of-bounds write issue was addressed with improved bounds checking. apple · ipados, apple · iphone_os, apple · macos +3 2026-05-11 medium4.7 CVE-2026-43659 A race condition was addressed with additional validation. apple · ipados, apple · iphone_os, apple · macos +1 2026-05-11 medium6.2 CVE-2026-43653 The issue was addressed with improved memory handling. apple · ipados, apple · iphone_os, apple · macos +1 2026-05-11 medium4.3 CVE-2026-39869 The issue was addressed with improved memory handling. apple · ipados, apple · iphone_os, apple · macos +3 2026-05-11 medium5.5 CVE-2026-28996 A race condition was addressed with additional validation. apple · ipados, apple · iphone_os, apple · macos +3 2026-05-11 medium5.3 CVE-2026-28994 A use after free issue was addressed with improved memory management. apple · ipados, apple · iphone_os, apple · macos +2 2026-05-11 medium5.5 CVE-2026-28993 This issue was addressed by adding an additional prompt for user consent. apple · ipados, apple · iphone_os, apple · macos +1 2026-05-11 medium4.7 CVE-2026-28992 A memory corruption vulnerability was addressed with improved locking. apple · ipados, apple · iphone_os, apple · macos +3 2026-05-11 medium5.5 CVE-2026-28988 A permissions issue was addressed with additional restrictions. apple · ipados, apple · iphone_os, apple · macos +2 2026-05-11

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.