NetSight

Security Dashboard

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

Reset
8,098 matching advisories · page 7 of 270Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.4 CVE-2026-58804 In ExecuteGraphCommand of multiple files, there is a possible way to trigger an out of bounds write via an oversized scratch memory declaration due to an incor… Google · Android 11 days ago high8.8 CVE-2026-58798 In multiple functions of cn_Tai.cpp, there is a possible way to trigger an out of bounds write due to memory corruption. Google · Android 11 days ago high8.4 CVE-2026-58796 In multiple functions of AndroidManifest.xml, there is a possible way to trigger unauthorized firmware updates via exported broadcast receivers due to a missin… Google · Android 11 days ago high7.8 CVE-2026-58791 In pic_timing of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. Google · Android 11 days ago high7.8 CVE-2026-58790 In CMD_ENC_SET_PARAM of encoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. Google · Android 11 days ago high7.5 CVE-2026-58789 In s_gen_tile_param of multiple files, there is a possible way to trigger an out of bounds write in tile parameter arrays due to an incorrect bounds check. Google · Android 11 days ago high8.4 CVE-2026-58788 In stpropnci_process_std of stpropnci_std.cc, there is a possible way to trigger an out of bounds write into global state due to a missing bounds check. Google · Android 11 days ago high8.8 CVE-2026-58787 In chppWifiRangingEventNotification of clients/wifi.c, there is a possible Heap Buffer Overflow due to a logic error in the code. Google · Android 11 days ago high7.8 CVE-2026-58786 In cnm_memset of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. Google · Android 11 days ago high7.8 CVE-2026-58757 In mfc_alloc_enc_roi_buffer of mfc_buf.c, there is a possible out-of-bounds write due to a heap buffer overflow. Google · Android 11 days ago high7.8 CVE-2026-58740 In BitmapImageBuffer of bitmap_image_buffer.h, there is a possible out-of-bounds write due to an integer overflow. Google · Android 11 days ago high7.8 CVE-2026-58697 In codec3p_secure of codec3p_secure, there is a possible Heap Buffer Overflow due to a missing bounds check. Google · Android 11 days ago high7.8 CVE-2026-58690 In multiple functions of bitmap_image_buffer.h, there is a possible way to trigger an out of bounds write on the trusted execution environment heap due to an i… Google · Android 11 days ago high8.4 CVE-2026-58684 In smmu_config_l3tt of smmu.c, there is a possible permission bypass due to a logic error in the code. Google · Android 11 days ago high8.4 CVE-2026-57037 In getChppAppState of chpp_init.cc, there is a possible way to trigger an out of bounds read and corrupt task control structures due to a missing permission ch… Google · Android 11 days ago high8.4 CVE-2026-57036 In send_vdu_directive of gdmc/gsp/dev/bmsm/plat/lga/vdu.c, there is a possible Logic error due to a logic error in the code. Google · Android 11 days ago high8.4 CVE-2026-57009 In GC2AvcDec of GC2AvcDec.cpp, there is a possible Logic error due to a logic error in the code.... Google · Android 11 days ago high8.8 CVE-2026-57005 In EuiccPort.buildUiccAccessRule of EuiccPort.java, there is a possible Confused Deputy due to a confused deputy. Google · Android 11 days ago high8.4 CVE-2026-57004 In PresenceDecoderV1::DecodeDataElements of presence_decoder_v1.cc, there is a possible out-of-bounds write due to a missing bounds check. Google · Android 11 days ago high8.4 CVE-2026-56980 In createDataFlowAsync of data_flow_manager.cc, there is a possible way to trigger an out of bounds write in shared memory due to an integer overflow. Google · Android 11 days ago high7.8 CVE-2026-56969 In edgetpu_group_clear_responses of edgetpu_group.c, there is a possible Use After Free due to a logic error in the code. Google · Android 11 days ago high8.4 CVE-2026-56966 In CommitToBuffer of hal_override_options.bundle.cc, there is a possible way to retain stale direct memory access mappings to secure memory due to a confused d… Google · Android 11 days ago high8.4 CVE-2026-56951 In on_vkUpdateDescriptorSetWithTemplateSized2GOOGLE of vk_decoder_global_state.cpp, there is a possible way to leak host code pointers to a guest virtual machi… Google · Android 11 days ago high7.8 CVE-2026-56944 In smmu_detach_dev of private/google-modules/iommu/arm-smmu-v3/drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c, there is a possible Use After Free due to a lo… Google · Android 11 days ago high7.0 CVE-2026-56938 In port_shutdown of ipc.c, there is a possible Use After Free due to a race condition. This could... Google · Android 11 days ago high7.8 CVE-2026-56934 In arm_lpae_split_blk_unmap of drivers/iommu/io-pgtable-arm-common.c, there is a possible Logic error due to a logic error in the code. Google · Android 11 days ago high7.8 CVE-2026-56933 In RecordApTx of efw_ap_transport.c, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. Google · Android 11 days ago high7.8 CVE-2026-56929 In TrustyKeyMintManager::VerifyHat of trusty_keymint_manager.cc, there is a possible Security check bypass due to a logic error in the code. Google · Android 11 days ago high8.4 CVE-2026-56930 In smmu_find_ste of smmu.c, there is a possible way to retain stale translation lookaside buffer entries across stream identifiers due to a confused deputy. Google · Android 11 days ago high8.4 CVE-2026-56926 In multiple functions of PssSubscriptionManager.java, there is a possible way to spoof subscription switch results and trigger a device reboot due to a confuse… 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.