NetSight

Security Dashboard

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

Reset
8,098 matching advisories · page 13 of 270Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2026-58963 In multiple locations, there is a possible denial of service due to improper input validation.... Google · Android, google · android 19 days ago high8.4 CVE-2026-58962 In moveTaskToFrontLocked of ActivityTaskManagerService.java, there is a possible permission bypass due to a missing permission check. Google · Android, google · android 19 days ago high8.4 CVE-2026-58961 In moveTaskToFrontLocked of ActivityTaskManagerService.java, there is a possible background activity launch due to a logic error in the code. Google · Android, google · android 19 days ago high8.4 CVE-2026-58957 In resolveToHeavyWeightSwitcherIfNeeded of ActivityStarter.java, there is a possible background activity launch due to a confused deputy. Google · Android, google · android 19 days ago high8.4 CVE-2026-58956 In modpowF4 of avb_rsa.c, there is a possible signature verification bypass due to a logic error in the code. Google · Android, google · android 19 days ago high7.5 CVE-2026-58949 In parseMetaData of StagefrightMetadataRetriever.cpp, there is a possible denial of service due to a stack buffer overflow. Google · Android, google · android 19 days ago high8.4 CVE-2026-58946 In navigateUpTo of ActivityClientController.java, there is a possible permission bypass due to a logic error in the code. Google · Android, google · android 19 days ago high8.4 CVE-2026-58944 In moveTaskToFrontLocked of ActivityTaskManagerService.java, there is a possible background application launch (bal) issue due to a confused deputy. Google · Android, google · android 19 days ago high8.4 CVE-2026-58943 In run of AddAccountSettings.java, there is a possible background activity launch due to a confused deputy. Google · Android, google · android 19 days ago high8.4 CVE-2026-58942 In do_fault_around of memory.c, there is a possible use after free due to a logic error in the code. Google · Android, google · android 19 days ago high7.5 CVE-2026-58938 In parseChunk of MPEG4Extractor.cpp, there is a possible denial of service due to improper input validation. Google · Android, google · android 19 days ago high8.4 CVE-2026-58934 In prepareWindowToDisplayDuringRelayout of WindowState.java, there is a possible permission bypass due to a logic error in the code. Google · Android, google · android 19 days ago high7.8 CVE-2026-58886 In updateInputWindows of InputMonitor.java, there is a possible tapjacking issue due to a logic error in the code. Google · Android, google · android 19 days ago high8.4 CVE-2026-58885 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-58884 In startTetheredHotspotRequest of WifiServiceImpl.java, there is a possible permission bypass due to a confused deputy. Google · Android, google · android 19 days ago high7.5 CVE-2026-58883 In multiple locations, there is a possible denial of service due to a logic error in the code.... Google · Android, google · android 19 days ago high7.5 CVE-2026-58882 In decodeWapPdu of WapPushOverSms.java, there is a possible out of bounds read due to an integer overflow. Google · Android, google · android 19 days ago high8.4 CVE-2026-58879 In descramble of multiple files, there is a possible out-of-bounds write due to improper casting.... Google · Android, google · android 19 days ago high8.4 CVE-2026-58871 In set_type4_frame_classifier of sta_iface.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-58867 In getMessenger of WifiP2pServiceImpl.java, there is a possible permission bypass due to a missing permission check. Google · Android, google · android 19 days ago high8.4 CVE-2026-58866 In setAccessibilityWindowAttributes of AccessibilityWindowManager.java, there is a possible untrusted/misleading UI issue due to a missing permission check. Google · Android, google · android 19 days ago high8.1 CVE-2026-58857 In decrypt of CryptoHalHidl.cpp, there is a possible use-after-free due to a race condition. This... Google · Android, google · android 19 days ago high7.5 CVE-2026-58853 In multiple functions of ipphelper.c, there is a possible stack bugger overflow due to a missing bounds check. Google · Android, google · android 19 days ago high8.4 CVE-2026-58847 In kvm_vfio_pviommu_attach of vfio.c, there is a possible double free due to a logic error in the code. Google · Android, google · android 19 days ago high8.4 CVE-2026-58845 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-58844 In multiple locations, there is a possible out of bounds read/write due to an incorrect bounds check. Google · Android, google · android 19 days ago high8.4 CVE-2026-58837 In multiple locations, there is a possible background activity launch due to a logic error in the code. Google · Android, google · android 19 days ago high7.8 CVE-2026-58836 In handlePackagePostInstall of InstallPackageHelper.java, there is a possible Enhanced Confirmation Mode (ECM) bypass vulnerability that allows a sideloaded ap… Google · Android, google · android 19 days ago high8.4 CVE-2026-58829 In fuse_backing_mmap of backing.c, there is a possible memory corruption due to a use after free.... Google · Android, google · android 19 days ago high8.4 CVE-2026-58828 In multiple functions of base.c, there is a possible use-after-free due to a race condition. This... 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.