NetSight

Security Dashboard

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

Reset
579 matching advisories · page 1 of 20Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
low3.1 CVE-2026-130972 Observable discrepancy in PictureInPicture in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to leak cross-origin data via a crafted HTML page. Google · Chrome, google · chrome 4 days ago low3.1 CVE-2026-131012 Missing authorization in Services in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to obtain cross-or… Google · Chrome, google · chrome 4 days ago low3.1 CVE-2026-131052 Race condition in UI in Google Chrome on on Android prior to 158.0.8127.36 allowed a local attacker leveraging social engineering to obtain cross-origin data v… Google · Chrome, google · chrome 4 days ago low3.1 CVE-2026-130942 Observable discrepancy in Extensions in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to obtain cross-origin data via a crafted Chrome extensi… Google · Chrome, google · chrome 4 days ago low3.4 CVE-2026-131083 Uninitialized resource in GPU in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to potentially read me… Google · Chrome, google · chrome 4 days ago low3.4 CVE-2026-131002 Uninitialized resource in GPU in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to potentially read me… Google · Chrome, google · chrome 4 days ago low3.1 CVE-2026-131007 Uninitialized resource in GPU in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to obtain cross-origin… Google · Chrome, google · chrome 4 days ago low3.4 CVE-2026-131076 Uninitialized resource in GPU in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to read memory outside… Google · Chrome, google · chrome 4 days ago low3.4 CVE-2026-131103 Uninitialized resource in GPU in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to read memory outside… Google · Chrome, google · chrome 4 days ago low3.1 CVE-2026-130934 Incorrect authorization in Autofill in Google Chrome on on Android prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to… Google · Chrome, google · chrome 4 days ago low3.4 CVE-2026-130970 Uninitialized resource in GPU in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to read memory outside… Google · Chrome, google · chrome 4 days ago low3.5 CVE-2026-125711 The Widgets for Google Reviews WordPress plugin before 14.3, WP Tripadvisor Review Widgets WordPress plugin before 14.3, Widgets for Booking.com Reviews WordPr… Unknown · Widgets for Google Reviews, Unknown · WP Tripadvisor Review Widgets, Unknown · Widgets for Booking.com Reviews +17 8 days ago low3.1 CVE-2026-126841 Out of bounds read in Skia in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to read memory outside th… Google · Chrome, google · chrome 10 days ago low3.4 CVE-2026-126913 Out of bounds read in Compositing in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to read memory out… Google · Chrome, google · chrome 10 days ago low3.1 CVE-2026-126848 Uninitialized resource in Skia in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to read memory outsid… Google · Chrome, google · chrome 10 days ago low3.1 CVE-2026-126882 Information leak in Skia in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to leak cross-origin data v… Google · Chrome, google · chrome 10 days ago low3.1 CVE-2026-126922 Out of bounds read in Skia in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to leak cross-origin data… Google · Chrome, google · chrome 10 days ago low3.1 CVE-2026-126894 Out of bounds read in Skia in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to leak cross-origin data… Google · Chrome, google · chrome 10 days ago low3.1 CVE-2026-126844 Uninitialized resource in Skia in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to read memory outsid… Google · Chrome, google · chrome 10 days ago low3.1 CVE-2026-126907 Uninitialized resource in Media in Google Chrome on on Windows prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to pot… Google · Chrome, google · chrome 10 days ago low3.1 CVE-2026-126845 Uninitialized resource in GPU in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to potentially read me… Google · Chrome, google · chrome 10 days ago low3.1 CVE-2026-126853 Uninitialized resource in Skia in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to read memory outsid… Google · Chrome, google · chrome 10 days ago low3.3 CVE-2026-59637 In userdata_report of hwcodec_firmware, there is a possible Logic error due to a logic error in the code. Google · Android 11 days ago low2.3 CVE-2026-59619 In getCodecQp of GC2AV1Enc.cpp, there is a possible way to trigger an out of bounds read during quantization table lookup due to a missing bounds check. Google · Android 11 days ago low2.7 CVE-2026-59583 In FormCredentials of SipAuHelper.cpp, there is a possible way to disclose authentication credentials in cleartext via a scheme downgrade due to improper input… Google · Android 11 days ago low3.3 CVE-2026-59580 In trusty_context_switch of services/spd/trusty/trusty.c, there is a possible Secure world register state leak due to a logic error in the code. Google · Android 11 days ago low2.4 CVE-2026-59574 In notifyPollingLoopFrames of hal_fwlog.cc, there is a possible way to trigger an out of bounds read and write when formatting firmware log notifications due t… Google · Android 11 days ago low3.3 CVE-2026-58812 In decode of fw_vp9_dec_pic.c, there is a possible Logic error due to a logic error in the code.... Google · Android 11 days ago low2.3 CVE-2026-58810 In multiple functions of simd_ctx.c, there is a possible way to disclose secure vector predicate and fault registers to non-secure callers due to uninitialized… Google · Android 11 days ago low2.3 CVE-2026-58808 In multiple locations, there is a possible way to dump secure cache lines into non-secure memory on warm reset due to a missing permission check. 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.