NetSight

Security Dashboard

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

Reset
8,098 matching advisories · page 6 of 270Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2026-95402 In slice_header 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-95401 In knee_function_info of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. Google · Android 11 days ago high8.4 CVE-2026-95400 In StNfc_hal_write of hal_st21nfc.cc, there is a possible way to trigger an out of bounds write into global memory due to an incorrect bounds check. Google · Android 11 days ago high7.8 CVE-2026-95397 In sub_layer_hrd_parameters 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-59635 In cpb_cnt of avc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow.... Google · Android 11 days ago high7.5 CVE-2026-59632 In RespondReceivedMessage of MtsMessageController.cpp, there is a possible way to trigger memory exhaustion via an undrained message queue due to a type confus… Google · Android 11 days ago high7.8 CVE-2026-59631 In s_inter_rps_pred of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. Google · Android 11 days ago high8.4 CVE-2026-59630 In check_constraint_monotonicity of lib.rs, there is a possible way to downgrade stored security policies and bypass rollback protection due to a logic error. Google · Android 11 days ago high7.5 CVE-2026-59623 In CompareTelUris of SipAddress.cpp, there is a possible way to trigger an unhandled out of range exception and process crash due to an incorrect bounds check. Google · Android 11 days ago high7.8 CVE-2026-59616 In prev_run_vcore of hwcodec_firmware, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. Google · Android 11 days ago high7.5 CVE-2026-59613 In multiple locations, there is a possible way to trigger an out of bounds read and temporary denial of service due to improper input validation. Google · Android 11 days ago high7.8 CVE-2026-59612 In buffering_period of avc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. Google · Android 11 days ago high7.5 CVE-2026-59611 In multiple locations, there is a possible way to trigger a temporary denial of service via an integer overflow trap due to improper input validation. Google · Android 11 days ago high8.4 CVE-2026-59609 In fence_manager_extract_iif of fence_manager.c, there is a possible way to corrupt kernel memory via fence identifier reuse due to a use after free. Google · Android 11 days ago high7.8 CVE-2026-59608 In tone_mapping_info 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-59607 In TzPipelineInputExtractor of TzPipelineInputExtractor.cpp, there is a possible Logic check bypass due to a logic error in the code. Google · Android 11 days ago high7.5 CVE-2026-59603 In RespondReceivedMessage of MtsMessageController.cpp, there is a possible way to trigger a double free and process abort during message retry handling due to … Google · Android 11 days ago high7.8 CVE-2026-59598 In platform_rio_ncp_wdt_handler of edgetpu_rio.c, there is a possible Use After Free due to a use after free. Google · Android 11 days ago high8.4 CVE-2026-59597 In bindDataService of DataServiceManager.java, there is a possible way to retain privileged tunnel management permissions across configuration updates due to a… Google · Android 11 days ago high8.4 CVE-2026-59596 In multiple functions of mpu.c, there is a possible way to execute code from non-secure memory in the security coprocessor due to an insecure default value. Google · Android 11 days ago high7.5 CVE-2026-59595 In DecodeHeaderComponent of SipStack.cpp, there is a possible way to trigger stack exhaustion via unbounded mutual recursion due to a resource exhaustion. Google · Android 11 days ago high7.8 CVE-2026-59594 In spm_alloc of encoder, there is a possible Heap Buffer Overflow due to a heap buffer overflow.... Google · Android 11 days ago high7.8 CVE-2026-59593 In tile_info of av1_decoder, there is a possible Heap Buffer Overflow due to a heap buffer overflow. Google · Android 11 days ago high8.4 CVE-2026-59587 In stpropnci_prop_st_build_set_custom_polling_cmd of stpropnci_prop_st.cc, there is a possible way to trigger an out of bounds write into global memory due to … Google · Android 11 days ago high7.8 CVE-2026-59589 In s_av1_dec_metadata_scalability of av1_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. Google · Android 11 days ago high7.5 CVE-2026-59585 In SetDisplayName of RegInfoContact.cpp, there is a possible denial of service due to a missing null check. Google · Android 11 days ago high7.5 CVE-2026-59582 In StartTimer of UcePublishManager.cpp, there is a possible way to trigger a process abort during timer calculation due to an integer overflow. Google · Android 11 days ago high7.8 CVE-2026-59578 In s_check_valid_tile_param_custom_tile of av1_encoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. Google · Android 11 days ago high7.8 CVE-2026-59573 In max_num_ref_frames of avc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. Google · Android 11 days ago high7.5 CVE-2026-58807 In Retry_MtsMessageInPending of MtsMessageController.cpp, there is a possible way to trigger memory exhaustion via leaked message objects due to a logic error. 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.