NetSight

Security Dashboard

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

Reset
7,954 matching advisories · page 9 of 266Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2026-121038 Information leak in Compositing in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to obtain cross-origin data via a crafted HTML page. Google · Chrome, google · chrome 18 days ago medium6.5 CVE-2026-121051 UI misrepresentation in iOSWeb in Google Chrome on on iOS prior to 157.0.8103.38 allowed a remote attacker to spoof address bar via a crafted HTML page. Google · Chrome, google · chrome 18 days ago medium6.7 CVE-2026-58977 In is_valid_header of timed_cache_item.c, there is a possible out-of-bounds write due to a missing bounds check. Google · Android, google · android 19 days ago medium6.7 CVE-2026-58927 The vulnerability is a Use-After-Free (UAF) in the EVS AIDL HAL, arising from a data race on an unsynchronized `std::weak_ptr` within `EvsEnumerator::openCamer… Google · Android, google · android 19 days ago medium6.1 CVE-2026-58915 A physical occupant on an Android Automotive OS (AAOS) Multi-User Multi-Display (MUMD) passenger display can view sensitive Heads-Up Notification (HUN) content… Google · Android, google · android 19 days ago medium5.5 CVE-2026-49903 The `ClusterRenderingService.dump()` method, accessible to processes holding `android.permission.DUMP` and `android.permission.PACKAGE_USAGE_STATS`, acts as a … Google · Android, google · android 19 days ago medium5.5 CVE-2026-59048 In rb_cpu_init of trace.c, there is a possible out-of-bounds read due to an incorrect bounds check. Google · Android, google · android 19 days ago medium6.2 CVE-2026-59047 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 medium6.2 CVE-2026-59046 In __pkvm_guest_relinquish_to_host of mem_protect.c, there is a possible out-of-bounds write due to improper input validation. Google · Android, google · android 19 days ago medium6.2 CVE-2026-59031 In InputDispatcher::flushSensor of InputDispatcher.cpp, there is a possible denial of service due to a logic error in the code. Google · Android, google · android 19 days ago medium5.5 CVE-2026-59022 In multiple functions of MediaProvider.java, there is a possible permission bypass due to a logic error in the code. Google · Android, google · android 19 days ago medium6.2 CVE-2026-59021 In multiple locations, there is a possible denial of service due to improper input validation.... Google · Android, google · android 19 days ago medium5.9 CVE-2026-59020 In removeUserData of DevicePolicyManagerService.java, there is a possible denial of service due to a race condition. Google · Android, google · android 19 days ago medium4.0 CVE-2026-59015 In multiple locations, there is a possible permission bypass due to a confused deputy. This could... Google · Android, google · android 19 days ago medium5.5 CVE-2026-59012 In checkLastKnownCellIdAccessPermission of TelephonyPermissions.java, there is a possible permission bypass due to a missing permission check. Google · Android, google · android 19 days ago medium5.5 CVE-2026-59011 In multiple locations, there is a possible permission bypass due to a logic error in the code.... Google · Android, google · android 19 days ago medium6.2 CVE-2026-59010 In deserialize of legacy.rs, there is a possible denial of service due to a missing bounds check.... Google · Android, google · android 19 days ago medium6.2 CVE-2026-59008 In setApplicationRestrictions of DevicePolicyManagerService.java, there is a possible denial of service due to resource exhaustion. Google · Android, google · android 19 days ago medium5.3 CVE-2026-59007 In decode_packed_entry_number of codebook.c, there is a possible out-of-bounds read due to a logic error in the code. Google · Android, google · android 19 days ago medium5.0 CVE-2026-59006 In getTouchOcclusionMode of WindowState.java, there is a possible tapjacking issue due to a tapjacking/overlay attack. Google · Android, google · android 19 days ago medium4.0 CVE-2026-59003 In getSubscriptionProperty of SubscriptionManagerService.java, there is a possible information disclosure due to a missing permission check. Google · Android, google · android 19 days ago medium4.6 CVE-2026-59002 In handleMessage of UsbDeviceManager.java, there is a possible lock-screen bypass due to a logic error in the code. Google · Android, google · android 19 days ago medium4.0 CVE-2026-59001 In checkQueryPermission of TelephonyProvider.java, there is a possible permission bypass due to a logic error in the code. Google · Android, google · android 19 days ago medium4.0 CVE-2026-58997 In validateImageInfo of Bitmap.cpp, there is a possible out-of-bounds read due to a precondition check failure. Google · Android, google · android 19 days ago medium5.3 CVE-2026-58990 In l2c_fcr_process_peer_cfg_req of l2c_fcr.cc, there is a possible memory safety issue due to an integer overflow. Google · Android, google · android 19 days ago medium4.0 CVE-2026-58988 In isValid of ShimConverter.cpp, there is a possible out of bounds read due to a missing bounds check. Google · Android, google · android 19 days ago medium6.2 CVE-2026-58985 In handleConnectInternal of RpcServerTrusty.cpp, there is a possible denial of service due to a logic error in the code. Google · Android, google · android 19 days ago medium6.8 CVE-2026-58978 In multiple locations, there is a possible permission bypass due to a logic error in the code.... Google · Android 19 days ago medium4.0 CVE-2026-58976 In getSelectionBySubIds of ProviderUtil.java, there is a possible cross-user data leak due to a logic error in the code. Google · Android 19 days ago medium4.0 CVE-2026-58971 In _mupdf_get_hdr of wprint_mupdf.c, there is a possible out-of-bounds read due to an integer overflow. 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.