NetSight

Security Dashboard

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

Reset
7,956 matching advisories · page 22 of 266Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2026-56975 In Cellular Modem, there is a possible denial of service due to improper input validation. google · android 2026-09-15 medium6.7 CVE-2026-56973 In multiple locations, there is a possible escalation of privilege due to a logic error in the code. google · android 2026-09-15 medium6.7 CVE-2026-56972 In multiple locations, there is a possible out-of-bounds write due to an incorrect bounds check. google · android 2026-09-15 medium6.4 CVE-2026-56964 In multiple locations, there is a possible use-after-free due to a race condition. google · android 2026-09-15 medium5.5 CVE-2026-56958 In gf_algo_get_cached_dump_data of gf_algo.c, there is a possible out-of-bounds read due to a missing bounds check. google · android 2026-09-15 medium4.4 CVE-2026-56950 In validate_ns_buf of mbu_class.rs, there is a possible information disclosure due to improper input validation. google · android 2026-09-15 medium6.7 CVE-2026-56932 In Trusted Execution Environment, there is a possible memory corruption due to improper input validation. google · android 2026-09-15 medium6.4 CVE-2026-56923 In handle_unmap_req of tipc_virtio_dev.c, there is a possible memory corruption due to a race condition. google · android 2026-09-15 medium6.7 CVE-2026-56922 In CPM, there is a possible permission bypass due to a confused deputy. google · android 2026-09-15 medium6.4 CVE-2026-56915 In bigo_worker_thread of bigo.c, there is a possible escalation of privilege due to a race condition. google · android 2026-09-15 medium6.7 CVE-2026-56907 In VPU, there is a possible shared memory overwrite due to improper input validation. google · android 2026-09-15 medium6.2 CVE-2026-56892 In ReadDataElement of common.c, there is a possible information disclosure due to an incorrect bounds check. google · android 2026-09-15 medium6.7 CVE-2026-56889 In multiple locations, there is a possible permission bypass due to an integer overflow. google · android 2026-09-15 medium6.2 CVE-2026-56888 In multiple locations, there is a possible permission bypass due to side channel information disclosure. google · android 2026-09-15 medium6.7 CVE-2026-56879 In gmc_mb_msg_handler of gmc_mba.c, there is a possible memory corruption due to a confused deputy. google · android 2026-09-15 medium6.7 CVE-2026-55365 In multiple functions of remap.c, there is a possible out-of-bounds write due to an incorrect bounds check. google · android 2026-09-15 medium6.7 CVE-2026-55332 In multiple locations, there is a possible out-of-bounds write due to improper input validation. google · android 2026-09-15 medium6.7 CVE-2026-55317 In printf of printf.c, there is a possible out-of-bounds write due to improper input validation. google · android 2026-09-15 medium6.7 CVE-2026-55304 In addr_remap_address_map of remap.c, there is a possible escalation of privilege due to a logic error in the code. google · android 2026-09-15 medium6.7 CVE-2026-55302 In multiple locations, there is a possible permission bypass due to a logic error in the code. google · android 2026-09-15 medium4.4 CVE-2026-0197 In VPU, there is a possible information dislclosure due to a logic error in the code. google · android 2026-09-15 medium6.7 CVE-2026-0192 In Bootloader, there is a possible escalation of privilege due to a missing permission check. google · android 2026-09-15 medium6.7 CVE-2026-0187 In gsa_sw_pk_hash_compare of image-auth-srv.c, there is a possible escalation of privilege due to a logic error in the code. google · android 2026-09-15 medium6.7 CVE-2026-0186 In ac_init_one_sswrp of init.c, there is a possible escalation of privilege due to a logic error in the code. google · android 2026-09-15 medium4.4 CVE-2026-0183 In CPM, there is a possible information disclosure due to a confused deputy. google · android 2026-09-15 medium6.7 CVE-2026-0179 In Bootloader, there is a possible permission bypass due to a missing permission check. google · android 2026-09-15 medium4.4 CVE-2026-0177 In do_sss_aes_gcm_256_op of crypto-aes.c, there is a possible out-of-bounds read due to a missing bounds check. google · android 2026-09-15 medium4.3 CVE-2026-89050 The Quads Ads Manager for Google AdSense WordPress plugin before 3.0.5 does not verify payment completion with the configured payment gateway before marking an… Quads Ads Manager for Google AdSense WordPress plugin 2026-09-13 medium4.3 CVE-2026-62139 Unauthenticated Cross Site Request Forgery (CSRF) in Site Kit by Google <= 1.186.0 versions. Site Kit by Google 2026-09-11 medium6.4 CVE-2026-4657 The Easy Google Fonts plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the control_selectors meta field in all versions up to, and includi… 2026-09-10

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.