NetSight

Security Dashboard

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

Reset
61 matching advisories · page 2 of 3Index updated 11 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.1 CVE-2026-34774 Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. npm · electron 2026-04-03 medium4.7 CVE-2026-34773 Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. npm · electron 2026-04-03 medium5.8 CVE-2026-34772 Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. npm · electron 2026-04-03 high7.5 CVE-2026-34771 Electron: Use-after-free in WebContents fullscreen, pointer-lock, and keyboard-lock permission callbacks npm · electron 2026-04-03 high7.0 CVE-2026-34770 Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. npm · electron 2026-04-03 high7.7 CVE-2026-34769 Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. npm · electron 2026-04-03 low3.9 CVE-2026-34768 Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. npm · electron 2026-04-03 medium5.9 CVE-2026-34767 Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. npm · electron 2026-04-03 low3.3 CVE-2026-34766 Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. npm · electron 2026-04-03 medium6.1 CVE-2023-44402 ASAR Integrity bypass via filetype confusion in electron npm · electron 2023-12-01 medium6.1 CVE-2023-39956 Electron vulnerable to out-of-package code execution when launched with arbitrary cwd npm · electron 2023-09-06 medium6.0 CVE-2023-29198 Electron context isolation bypass via nested unserializable return value npm · electron 2023-09-06 high7.5 CVE-2023-23623 Electron's Content-Secrity-Policy disabling eval not applied consistently in renderers with sandbox disabled npm · electron 2023-09-06 high7.2 CVE-2022-36077 Exfiltration of hashed SMB credentials on Windows via file:// redirect npm · electron 2022-11-08 medium6.6 CVE-2022-29257 Electron is a framework for writing cross-platform desktop applications using JavaScript (JS), HTML, and CSS. npm · electron 2022-06-13 low2.2 CVE-2022-29247 Electron is a framework for writing cross-platform desktop applications using JavaScript (JS), HTML, and CSS. npm · electron 2022-06-13 low3.4 CVE-2022-21718 Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. npm · electron 2022-03-22 medium6.8 CVE-2021-39184 Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. npm · electron 2021-10-12 high8.8 CVE-2021-32772 Poddycast is a podcast app made with Electron. electronjs · poddycast 2021-08-03 medium5.4 CVE-2020-26272 The Electron framework lets users write cross-platform desktop applications using JavaScript, HTML and CSS. npm · electron 2021-01-28 critical9.0 CVE-2020-35717 zonote through 0.4.0 allows XSS via a crafted note, with resultant Remote Code Execution (because nodeIntegration in webPreferences is true). electronjs · zonote 2021-01-01 medium5.6 CVE-2020-15215 Electron before versions 11.0.0-beta.6, 10.1.2, 9.3.1 or 8.5.2 is vulnerable to a context isolation bypass. npm · electron 2020-10-06 high7.5 CVE-2020-15174 In Electron before versions 11.0.0-beta.1, 10.0.1, 9.3.0 or 8.5.1 the `will-navigate` event that apps use to prevent navigations to unexpected destinations as … npm · electron 2020-10-06 medium6.8 CVE-2020-4075 In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, arbitrary local file read is possible by defining unsafe window options on a child window opened vi… npm · electron 2020-07-07 high7.7 CVE-2020-4077 In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, there is a context isolation bypass. npm · electron 2020-07-07 high7.8 CVE-2020-4076 In Electron before versions 7.2.4, 8.2.4, and 9.0.0-beta21, there is a context isolation bypass. npm · electron 2020-07-07 medium6.8 CVE-2020-15096 In Electron before versions 6.1.1, 7.2.4, 8.2.4, and 9.0.0-beta21, there is a context isolation bypass, meaning that code running in the main world context in … npm · electron 2020-07-07 high8.1 CVE-2018-15685 GitHub Electron 1.7.15, 1.8.7, 2.0.7, and 3.0.0-beta.6, in certain scenarios involving IFRAME elements and "nativeWindowOpen: true" or "sandbox: true" options,… npm · electron 2018-08-23 critical9.8 CVE-2017-16151 Based on details posted by the ElectronJS team; A remote code execution vulnerability has been discovered in Google Chromium that affects all recent versions o… npm · electron 2018-06-07 high8.1 CVE-2018-1000136 Electron version 1.7 up to 1.7.12; 1.8 up to 1.8.3 and 2.0.0 up to 2.0.0-beta.3 contains an improper handling of values vulnerability in Webviews that can resu… npm · electron 2018-03-23

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.