NetSight

Security Dashboard

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

Reset
7,954 matching advisories · page 5 of 266Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.2 CVE-2026-59575 In stpropnci_cb_observe_mode_suspend of stpropnci_prop_android.cc, there is a possible way to trigger an out of bounds write into global state due to a missing… Google · Android 11 days ago medium6.7 CVE-2026-58813 In mmap of mman.c, there is a possible way to trigger an out of bounds read and write via mapping size truncation due to an incorrect bounds check. Google · Android 11 days ago medium4.0 CVE-2026-58811 In smmu_get_mair_idx of smmu.c, there is a possible way to apply incorrect memory attributes to direct memory access mappings due to a logic error. Google · Android 11 days ago medium6.7 CVE-2026-58809 In smmu_domain_config_s1 of arm-smmu-v3.c, there is a possible OOB Write due to a missing bounds check. Google · Android 11 days ago medium6.7 CVE-2026-58805 In multiple locations, there is a possible way to zero arbitrary secure memory via unvalidated image body addresses due to a missing bounds check. Google · Android 11 days ago medium6.7 CVE-2026-58785 In update_user_consent of main.rs, there is a possible elevation of privilege due to uninitialized data. Google · Android 11 days ago medium4.4 CVE-2026-58783 In multiple locations, there is a possible denial of service due to a logic error in the code.... Google · Android 11 days ago medium6.2 CVE-2026-58782 In multiple locations, there is a possible denial of service due to a logic error in the code.... Google · Android 11 days ago medium6.7 CVE-2026-58781 In HostLinkBase::chreIpiHandler of host_link.cc, there is a possible out-of-bounds write due to a missing bounds check. Google · Android 11 days ago medium6.7 CVE-2026-58779 In multiple locations, there is a possible permission bypass due to a logic error in the code.... Google · Android 11 days ago medium6.4 CVE-2026-58778 In multiple locations, there is a possible use-after-free due to a race condition. This could... Google · Android 11 days ago medium6.2 CVE-2026-58752 In aoc_unlocked_ioctl_handle_ion_fd of aoc.c, there is a possible type confusion due to improper input validation. Google · Android 11 days ago medium6.7 CVE-2026-58729 In multiple files, there is a possible out-of-bounds write due to a missing bounds check. This... Google · Android 11 days ago medium4.0 CVE-2026-58702 In createIntent of TimerAgent.java, there is a possible permission bypass due to a confused deputy. Google · Android 11 days ago medium6.7 CVE-2026-58696 In multiple locations, there is a possible out-of-bounds write due to a heap buffer overflow.... Google · Android 11 days ago medium6.7 CVE-2026-58680 In cpm_mbox_power_ctrl_sswrp of cpm_mbox.c, there is a possible permission bypass due to a precondition check failure. Google · Android 11 days ago medium6.8 CVE-2026-58677 In get_secure_boot_mode of auth.rs, there is a possible way to bypass root signature verification via fault injection due to a logic error. Google · Android 11 days ago medium6.7 CVE-2026-57048 In authenticate of verify_image, there is a possible Signature verification logic bypass due to a logic error in the code. Google · Android 11 days ago medium6.7 CVE-2026-57043 In tipc_dev_probe of tipc_virtio_dev.c, there is a possible way to corrupt memory via an off-by-one cleanup loop on probe failure due to a logic error. Google · Android 11 days ago medium6.7 CVE-2026-57013 In access_control_enable of multiple files, there is a possible way to release secure coprocessors from reset via unclaimed firewall registers due to an insecu… Google · Android 11 days ago medium6.7 CVE-2026-56995 In multiple locations, there is a possible way to corrupt host allocator metadata in shared memory due to memory corruption. Google · Android 11 days ago medium5.3 CVE-2026-56956 In EncodeT140 of TextRtpPayloadEncoderNode.cpp, there is a possible Heap Buffer Overflow due to a logic error in the code. Google · Android 11 days ago medium6.4 CVE-2026-56949 In multiple locations, there is a possible way to modify authenticated coprocessor firmware in shared memory before loading due to a race condition. Google · Android 11 days ago medium4.0 CVE-2026-56947 In getCarrierRestrictionStatus of PhoneInterfaceManager.java, there is a possible permission bypass due to a confused deputy. Google · Android 11 days ago medium6.7 CVE-2026-56946 In smmu_unmap_visit_leaf of arm-smmu-v3.c, there is a possible way to release active direct memory access page references during unmapping due to a logic error. Google · Android 11 days ago medium4.0 CVE-2026-56935 In km_os_regen_salt of storage.c, there is a possible way to recover deleted keys due to a logic error. Google · Android 11 days ago medium6.7 CVE-2026-56911 In handle_fips_hmac_req of hwcrypto_proxy.c, there is a possible heap buffer overflow due to missing bounds check. Google · Android 11 days ago medium6.7 CVE-2026-56909 In multiple functions of sswrp_cpm.dtsi, there is a possible way to modify voltage control registers from non-secure software due to a missing permission check. Google · Android 11 days ago medium4.0 CVE-2026-56902 In multiple locations, there is a possible information disclosure due to a logic error in the code. Google · Android 11 days ago medium4.0 CVE-2026-56897 In multiple functions of attestation_object.c, there is a possible way to disclose uninitialized secure element stack memory in key attestation certificates du… Google · Android 11 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.