Skip to main content

Microsoft Edge CVE-2026-50521

| EUVDEUVD-2026-41137 HIGH
Use After Free (CWE-416)
2026-07-01 microsoft GHSA-q4g4-rw2v-x4v7
8.3
CVSS 3.1 · Vendor: microsoft
Temporal: 7.2
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain authorized/low-privilege browser context
  2. Delivery
    Deliver crafted web content to Edge
  3. Exploit
    Trigger use-after-free on freed object
  4. Execution
    Reclaim heap and control dangling pointer
  5. Impact
    Execute arbitrary code in browser process

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to hold some level of authorization (CVSS PR:L, and the description explicitly calls the actor an 'authorized attacker'), meaning it is not a fully unauthenticated internet-wide attack; the exact privilege - such as a logged-in browser session, a compromised low-privilege renderer, or authenticated access to attacker-served content - is not specified in the provided data and should be confirmed via the MSRC advisory. The vector lists UI:N, but as a browser use-after-free the realistic trigger is the victim's Edge instance processing attacker-controlled web content, which is a practical limiting factor. Additional limits: only Chromium-based Microsoft Edge is affected, the exploit maturity is Unproven (E:U) with no public exploit, and an official patch (RL:O) is already available, so updated installations are not exposed.

Impact

The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L yields 8.3 (High), driven by network reachability, low complexity, and high confidentiality/integrity impact, offset by a requirement for some privilege (PR:L) and only partial availability impact (A:L). Crucially, the temporal metrics E:U/RL:O/RC:C indicate Unproven exploit maturity, an Official fix, and a Confirmed report - so despite the high base score, there is no public exploit identified and it is not in CISA KEV, lowering near-term real-world exploitation risk. No EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be quantified here. Note a data tension worth verifying: the vector specifies UI:N (no user interaction) yet browser use-after-free bugs realistically require the victim to render attacker-controlled web content, and the description labels the actor an 'authorized attacker' (PR:L) without clarifying what privilege is required - confirm the exploitation preconditions against the MSRC advisory before prioritization.

Exploit ScenarioDerived

An attacker lures or directs a targeted Edge user to attacker-controlled web content (or leverages an already-authorized foothold implied by PR:L) that triggers the use-after-free, corrupting heap memory to hijack a freed object and execute code in the browser process. Given AC:L, the trigger is reliable once the vulnerable code path is reached, but the temporal metric E:U indicates no public exploit code exists at time of analysis, so exploitation would require original vulnerability-research effort.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.8% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 01, 2026

Remote code execution in Microsoft Edge (Chromium-based) stems from a use-after-free (CWE-416) memory-corruption flaw that lets an authorized attacker run arbitrary code over a network within the browser process. Microsoft has shipped an official fix and rates it CVSS 8.3; the exploit-maturity metric is Unproven (E:U), meaning no public exploit identified at time of analysis and it is not listed in CISA KEV. Impact is high to confidentiality and integrity with partial availability loss, making it a meaningful but not emergency patch priority for Edge-based endpoints.

RemediationAI

Apply the vendor fix: Patch available per vendor advisory - update Microsoft Edge to the current patched Stable channel build via Edge's built-in update mechanism (edge://settings/help) or your enterprise update ring/WSUS/Intune deployment, referencing https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50521 for the exact fixed version, which is not enumerated in the provided data. Because Edge auto-updates by default, ensure automatic updates are not disabled by policy and force a browser restart to complete installation. As a compensating control until patched, restrict browsing to trusted sites (block untrusted web content at a secure web gateway or via SmartScreen/URL allowlisting) to reduce exposure to attacker-controlled pages that could trigger the use-after-free - trade-off being reduced user browsing flexibility; no availability-safe workaround exists that preserves normal browser use, so patching is the definitive remedy.

Affected VersionsENISA

Microsoft Edge (Chromium-based) 1.0.0.0 <149.0.4022.68

Affected Packages

microsoft edge_149_0_4022_68 fix: Microsoft Edge (Chromium-based) 149.0.4022.68
euvd microsoft_edge_chromium_based fix: 149.0.4022.68

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in microsoft, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a use-after-free (CWE-416) in Microsoft Edge, which is built on the Chromium open-source engine (Blink rendering, V8 JavaScript). Use-after-free occurs when a program continues to reference heap memory after it has been freed, allowing an attacker who controls subsequent allocations to place crafted data in the reclaimed region and hijack a dangling pointer, typically leading to controlled code execution in the renderer or browser process. The affected product per the CPE is cpe:2.3:a:microsoft:microsoft_edge_(chromium-based), and the shared Chromium codebase means the underlying defect class frequently mirrors upstream Chromium/Google bugs, consistent with the 'Google' and 'Memory Corruption' tags on this record.

Know when Microsoft Edge Chromium Based gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 8.3 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
CIRCL (temporal) 7.2 HIGH
vuln.today AI 7.6 HIGH

Network-reachable low-complexity UAF, but browser exploitation realistically needs victim to render attacker content (UI:R) and some privilege (PR:L); C/I high, A partial per vendor.

3.1 AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:L
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

DescriptionCVE.org

Use after free in Microsoft Edge (Chromium-based) allows an authorized attacker to execute code over a network.

Executive ViewAI

Why It Matters

Microsoft Edge is affected by a high-severity remote code execution vulnerability (CVE-2026-50521, CVSS 8.3) that could allow attackers to execute arbitrary code within the browser process. No public exploit identified at time of analysis; however, successful exploitation could result in unauthorized access to sensitive data and compromise of affected user systems.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.8%
Top 47% exploitable
Prevalence
High
default browser bundled with Windows, broad enterprise and consumer footprint
Vendor Action
See Below
Required. The vulnerability documented by this CVE requires customer action to resolve.
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Social Media
3
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.8%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

43
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

CVE-2026-57983 CRITICAL
10.0 Jul 03

Security-feature bypass in Microsoft Edge (Chromium-based) versions prior to 150.0.4078.48 lets a remote, unauthenticate

CVE-2026-45495 CRITICAL
9.8 May 18

Remote code execution in Microsoft Edge (Chromium-based) lets an attacker run arbitrary code in the browser by getting a

CVE-2026-66321 CRITICAL
9.6 Aug 03

Remote code execution in Microsoft Edge (Chromium-based) before 151.0.4129.59 allows a network attacker to run arbitrary

CVE-2026-66312 HIGH
8.8 Aug 03

Remote code execution via buffer over-read in Microsoft Edge (Chromium-based) versions prior to 151.0.4129.59 affects au

CVE-2026-66326 HIGH
8.8 Aug 03

Remote code execution in Microsoft Edge (Chromium-based) prior to version 151.0.4129.59 is achievable by an unauthentica

CVE-2026-70341 HIGH
8.8 Sep 11

Use-after-free memory corruption in Microsoft Edge (Chromium-based) can let remote attackers execute arbitrary code in t

CVE-2026-57981 HIGH
8.8 Jul 03

Remote code execution in Microsoft Edge (Chromium-based) stems from a use-after-free memory corruption flaw (CWE-416) th

CVE-2026-57974 HIGH
8.8 Jul 03

Remote code execution in Microsoft Edge (Chromium-based) allows an unauthenticated attacker to run arbitrary code by lur

CVE-2026-56645 HIGH
8.8 Jul 03

Remote code execution in Microsoft Edge (Chromium-based) stems from a heap-based buffer overflow (CWE-122) that a networ

CVE-2026-72984 HIGH
8.8 Aug 28

Remote code execution in Microsoft Edge (Chromium-based) is enabled by a type confusion vulnerability (CWE-843) that can

CVE-2026-57985 HIGH
8.8 Jul 03

Remote code execution in Microsoft Edge (Chromium-based) before version 150.0.4078.48 allows an unauthenticated remote a

CVE-2026-58281 HIGH
8.3 Jul 11

Remote code execution in Microsoft Edge (Chromium-based) lets an unauthenticated network attacker run arbitrary code by

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy