NetSight

Security Dashboard

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

Reset
18,563 matching advisories · page 2 of 619Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2026-131005 Use after free in DevTools in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML pa… Google · Chrome, google · chrome 4 days ago medium4.3 CVE-2026-131035 Out of bounds read in Media in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to read memory inside the sandbox via a crafted HTML page. Google · Chrome, google · chrome 4 days ago high8.8 CVE-2026-131049 Use after free in SignIn in Google Chrome on on Windows prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to execute arbitrary cod… Google · Chrome, google · chrome 4 days ago medium5.4 CVE-2026-130949 UI misrepresentation in Passwords in Google Chrome on on Android prior to 158.0.8127.36 allowed a remote attacker to spoof UI elements via a crafted HTML page. Google · Chrome, google · chrome 4 days ago medium5.4 CVE-2026-130955 UI misrepresentation in Mobile in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to spoof address bar via a crafted HTML page. Google · Chrome, google · chrome 4 days ago medium5.3 CVE-2026-130973 Incorrect authorization in Sensor in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to obtain sensitiv… Google · Chrome, google · chrome 4 days ago medium6.5 CVE-2026-130981 Information leak in Enterprise in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to leak sensitive information via a crafted HTML page. Google · Chrome, google · chrome 4 days ago medium6.5 CVE-2026-130916 Missing authorization in DevTools in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to obtain sensitive informati… 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 high8.1 CVE-2026-131018 Confused deputy in DevTools in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to bypass web origin policy via a c… Google · Chrome, google · chrome 4 days ago medium4.3 CVE-2026-131027 Observable discrepancy in Browser in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to potentially obtain cross-origin data via a crafted HTML … Google · Chrome, google · chrome 4 days ago high8.1 CVE-2026-131029 Improper input validation in Extensions in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to bypass web origin policy into a privileged page vi… Google · Chrome, google · chrome 4 days ago medium5.4 CVE-2026-131085 Clickjacking in PermissionElement in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to spoof UI elements via a cr… Google · Chrome, google · chrome 4 days ago medium6.5 CVE-2026-131034 Incorrect authorization in SurfaceCapture in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to obtain sensitive i… Google · Chrome, google · chrome 4 days ago medium6.8 CVE-2026-130911 Race condition in DevTools in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to bypass web origin policy into a p… Google · Chrome 4 days ago high8.1 CVE-2026-130983 Incorrect authorization in DevTools in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to bypass web origin policy into a privileged page via a … Google · Chrome, google · chrome 4 days ago medium5.4 CVE-2026-131102 UI misrepresentation in FileSystem in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to spoof UI elements via a c… Google · Chrome, google · chrome 4 days ago medium4.3 CVE-2026-131105 Incorrect authorization in Glic in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to leak cross-origin data via a… Google · Chrome, google · chrome 4 days ago medium6.5 CVE-2026-131073 Incorrect authorization in Passwords in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to potentially obtain sensitive information via a crafte… Google · Chrome, google · chrome 4 days ago medium6.5 CVE-2026-130978 Incorrect authorization in Media in Google Chrome prior to 158.0.8127.36 allowed a local attacker to leak sensitive information via UI Interaction. Google · Chrome, google · chrome 4 days ago medium4.7 CVE-2026-131099 Out of bounds read in ANGLE in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to read memory outside the sandbox via a crafted HTML page. Google · Chrome, google · chrome 4 days ago medium4.2 CVE-2026-130908 Missing authorization in Passwords in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to bypass site is… Google · Chrome 4 days ago medium5.4 CVE-2026-131009 UI misrepresentation in Passwords in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to spoof UI elements via a crafted HTML page. Google · Chrome, google · chrome 4 days ago medium4.2 CVE-2026-130931 Incorrect authorization in Extensions in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to bypass syst… Google · Chrome, google · chrome 4 days ago medium6.5 CVE-2026-131072 Incorrect authorization in HID in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to leak sensitive information vi… Google · Chrome, google · chrome 4 days ago medium6.5 CVE-2026-130921 Nonce reuse in WebRTC in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to potentially obtain sensitive information via a crafted HTML page. Google · Chrome, google · chrome 4 days ago medium5.3 CVE-2026-130925 Race condition in Downloads in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to leak sensitive information via a… Google · Chrome, google · chrome 4 days ago medium6.5 CVE-2026-131040 Incorrect authorization in Extensions in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to obtain sensitive information via a crafted HTML page. Google · Chrome, google · chrome 4 days ago high7.4 CVE-2026-130912 Improper state validation in Network in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to potentially bypass web origin policy via crafted netw… Google · Chrome 4 days ago medium4.4 CVE-2026-131016 Incorrect authorization in DevTools in Google Chrome prior to 158.0.8127.36 allowed a local attacker to bypass system access restrictions via a crafted HTML pa… Google · Chrome, google · chrome 4 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.