27150 matches found
Chromium: CVE-2026-15110 Use after free in Extensions
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2026-15108 Integer overflow in Extensions API
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2026-15107 Use after free in IndexedDB
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2026-13282: Use after free in Payments
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2026-13282 Use after free in AdFilter
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2026-13037 Use after free in WebView
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2026-13032 Use after free in WebGL
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2026-13030 Uninitialized Use in GPU
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Chromium: CVE-2026-13028 Use after free in WebGL
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
CVE-2026-62828
Improper input validation in Microsoft Edge for Android allows an unauthorized attacker to perform tampering over a network...
CVE-2026-62828 Microsoft Edge for Android (Chromium-based) Tampering Vulnerability
...
EUVD-2026-49870
Improper input validation in Microsoft Edge for Android allows an unauthorized attacker to perform tampering over a network...
CVE-2026-62828
CVE-2026-62828 describes improper input validation in Microsoft Edge for Android (Chromium-based) that allows an unauthorized attacker to tamper over a network. The affected component is the browser on Android; the root cause is input validation weakness leading to tampering. The available docume...
CVE-2026-62828
Improper input validation in Microsoft Edge for Android allows an unauthorized attacker to perform tampering over a network...
CVE-2026-62828 Microsoft Edge for Android (Chromium-based) Tampering Vulnerability
...
Chromium: CVE-2026-15767 Heap buffer overflow in libyuv
This CVE was assigned by Chrome. Microsoft Edge Chromium-based ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information...
Solve Multi-CDN Entitlement Drift with Edge Functions Without Losing Viewers
...
CVE-2026-64646
A flaw was found in Next.js. An attacker sending specially crafted requests to a Next.js application utilizing the App Router with Server Actions configured to use the Edge runtime can cause excessive memory consumption. This can lead to a denial of service DoS due to resource exhaustion...
EUVD-2026-49845
Pivotick used plain JavaScript objects as lookup tables indexed by caller-controlled graph node identifiers in its tree-layout and cycle-detection components. Node identifiers matching properties inherited from Object.prototype, such as constructor, toString, or proto, were not handled as ordinar...
CVE-2026-66922
Pivotick CVE-2026-66922 affects the tree-layout and cycle-detection code by using plain JavaScript objects as lookup tables indexed with node identifiers that can collide with Object.prototype properties (e.g., constructor, toString, proto ). This can cause inherited-property confusion, wrong typ...