NetSight

Security Dashboard

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

Reset
8,098 matching advisories · page 12 of 270Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.4 CVE-2026-121197 Out of bounds read in ANGLE in Google Chrome on on Mac prior to 157.0.8103.38 allowed a remote attacker to read memory outside the sandbox via a crafted HTML p… Google · Chrome, google · chrome 18 days ago high8.8 CVE-2026-121107 Incorrect authorization in BackgroundFetch in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to bypass web origin policy via a crafted HTML pag… Google · Chrome, google · chrome 18 days ago high8.8 CVE-2026-121203 Use after free in Geometry in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML pa… Google · Chrome, google · chrome 18 days ago high8.4 CVE-2026-58873 In addDragDropListener of WindowManagerService.java, there is a possible permission bypass due to a missing permission check. Google · Android XR, google · android_xr 19 days ago high7.8 CVE-2026-58930 An unprivileged application can exploit a lack of package/signature validation in SystemUI's `RemoteQCController` when resolving a hardcoded `content://` URI. Google · Android, google · android 19 days ago high7.8 CVE-2026-58925 The report details a heap Use-After-Free (UAF) vulnerability within the `android.hardware.automotive.evs-default` HAL service, stemming from unsynchronized acc… Google · Android, google · android 19 days ago high7.5 CVE-2026-58924 The vulnerability is a heap out-of-bounds read in the EVS HAL's `getStreamList()` method. An... Google · Android, google · android 19 days ago high7.8 CVE-2026-49906 An unprivileged application can bypass the `android.car.permission.CAR_DISPLAY_IN_CLUSTER` permission by registering an activity with the `android.car.cluster.… Google · Android, google · android 19 days ago high7.4 CVE-2026-59045 In multiple locations, there is a possible memory corruption due to a race condition. This could... Google · Android, google · android 19 days ago high8.4 CVE-2026-59044 In multiple locations, there is a possible use-after-free due to a logic error in the code. This... Google · Android, google · android 19 days ago high7.4 CVE-2026-59043 In arm_lpae_split_blk_unmap of io-pgtable-arm-common.c, there is a possible memory corruption due to a race condition. Google · Android, google · android 19 days ago high7.4 CVE-2026-59042 In __pkvm_pages_to_ppages of mmu.c, there is a possible out-of-bounds write due to a race condition. Google · Android, google · android 19 days ago high8.4 CVE-2026-59028 In resolveAidConflictLocked of RegisteredAidCache.java, there is a possible permission bypass due to a confused deputy. Google · Android, google · android 19 days ago high8.4 CVE-2026-59016 In sendAnomalyProfile of ProfilingService.java, there is a possible path traversal issue due to path traversal. Google · Android, google · android 19 days ago high8.4 CVE-2026-59014 In multiple locations, there is a possible out-of-bounds write due to an integer overflow. This... Google · Android, google · android 19 days ago high8.4 CVE-2026-59005 In insertInternal of MmsProvider.java, there is a possible multiuser isolation issue due to a missing permission check. Google · Android, google · android 19 days ago high8.4 CVE-2026-59004 In multiple locations, there is a possible permission bypass due to an uncaught exception. This... Google · Android, google · android 19 days ago high8.4 CVE-2026-59000 In multiple locations, there is a possible permission bypass due to a confused deputy. This could... Google · Android, google · android 19 days ago high8.4 CVE-2026-58995 In getEntryFileName of ZipFileRO.cpp, there is a possible memory safety issue due to a heap buffer overflow. Google · Android, google · android 19 days ago high8.4 CVE-2026-58994 In multiple functions of NfcService.java, there is a possible permission bypass due to a missing permission check. Google · Android, google · android 19 days ago high8.4 CVE-2026-58989 In setOemUnlockAllowedByUser of OemLockService.java, there is a possible way to bypass FRP due to a missing permission check. Google · Android, google · android 19 days ago high8.4 CVE-2026-58986 In notifyPictureProfileHandleSelection of MediaQualityService.java, there is a possible permission bypass due to a missing permission check. Google · Android, google · android 19 days ago high8.4 CVE-2026-58984 In multiple locations, there is a possible memory corruption due to a use-after-free. This could... Google · Android, google · android 19 days ago high8.4 CVE-2026-58979 In canPresent of PresentationController.java, there is a possible permission bypass due to a logic error in the code. Google · Android 19 days ago high8.4 CVE-2026-58975 In multiple locations, there is a possible out-of-bounds write due to a missing bounds check.... Google · Android 19 days ago high8.4 CVE-2026-58974 In multiple locations, there is a possible permission bypass due to a missing permission check.... Google · Android 19 days ago high8.4 CVE-2026-58970 In deliverResult of AppTimeTracker.java, there is a possible background activity launch due to a confused deputy. Google · Android 19 days ago high8.4 CVE-2026-58966 In multiple functions of hppsfilter.c, there is a possible out-of-bounds write due to a stack buffer overflow. Google · Android, google · android 19 days ago high8.4 CVE-2026-58965 In handleAudioEffectBroadcast of MusicFxHelper.java, there is a possible permission bypass due to a confused deputy. Google · Android, google · android 19 days ago high8.4 CVE-2026-58964 In checkDestination of SmsUsageMonitor.java, there is a possible permission bypass due to improper input validation. Google · Android, google · android 19 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.