Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost crafted spoofing content
-
DeliveryVictim Edge reaches attacker content
-
ExploitAbuse improper access control (CWE-284)
-
ExecutionCross security-boundary scope change
-
PersistPresent spoofed trusted UI/origin
-
ImpactDeceive victim into trusting content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation targets Microsoft Edge (Chromium-based) over the network with no authentication (PR:N) and, per the CVSS vector, no user interaction flagged (UI:N); the primary limiting factor is high attack complexity (AC:H), meaning the attacker must satisfy conditions outside their control - likely a race, precise navigation timing, or a specific rendering state - for the spoof to land. The description does not name a specific feature toggle or non-default configuration, so the constraint is the AC:H reliability barrier rather than a config prerequisite. Caution: the combination of a spoofing/authentication-bypass impact with UI:N is atypical, since spoofing usually requires the victim to view attacker content - verify against Microsoft's advisory whether victim navigation is in practice required before assuming zero interaction. |
| Impact | The signals are mixed and should be read carefully. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:L) yields 8.1 'High' largely because of the scope change and high integrity impact combined with no privileges and no user interaction; however AC:H tells us successful exploitation depends on conditions the attacker does not fully control (timing, race, or victim navigation), which materially lowers real-world reliability. There is no CISA KEV entry and no evidence of public POC, so both exploitation-probability signals point low despite the high base score. No EPSS score or SSVC decision data was provided, so automatable/technical-impact cannot be independently derived - treat the 8.1 as a worst-case ceiling. Notably, UI:N is unusual for a spoofing/authentication-bypass class bug that normally requires a victim to visit a page; this apparent tension between UI:N and a spoofing impact should be verified against Microsoft's advisory before treating it as a no-interaction remote threat. Overall this is a patch-on-cycle priority for browser fleets, not an emergency, absent exploitation evidence. |
| Exploit ScenarioDerived | An attacker hosts or injects crafted web content that abuses the improper access-control flaw to render trusted-looking UI or content that appears to originate from a legitimate origin, then lures or races a victim's Edge browser into displaying it. Because the scope changes across a security boundary, the spoofed content can misrepresent a different origin or the browser chrome, enabling convincing phishing or trust manipulation. No public exploit code has been identified, and the AC:H rating means the attacker must win specific timing or configuration conditions for the spoof to succeed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 03, 2026
Spoofing in Microsoft Edge (Chromium-based) lets a remote, unauthenticated attacker misrepresent trusted UI or content to a victim by abusing improper access control (CWE-284), per Microsoft's own advisory (MSRC CVE-2026-58286). The high CVSS 8.1 is driven by a scope-changed impact (S:C) with high integrity effect, though the AC:H rating signals the attack is not trivially reliable. Currently there is no public exploit identified at time of analysis and no CISA KEV listing, so this is a proactively-patched issue rather than one under active exploitation.
RemediationAI
Apply the vendor patch: Microsoft has released a fix, and the primary action is to update Microsoft Edge (Chromium-based) to the patched build documented in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-58286 - the exact fixed version is not included in the supplied data and should be taken from that page. Ensure Edge automatic updates are enabled so the browser pulls the corrected Chromium channel; in managed environments push the update via Microsoft Update, Intune, WSUS, or your endpoint management tooling and confirm the deployed build meets or exceeds the advisory's fixed version. As an interim compensating control while patching is pending, restrict exposure by discouraging navigation to untrusted sites, enabling Enhanced Security Mode / SmartScreen, and user-awareness of address-bar and dialog cues; note these controls reduce but do not eliminate a spoofing vector and impose usability friction, so they are stopgaps rather than substitutes for the update.
Affected VersionsENISA
Affected Packages
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
Microsoft Edge (Chromium-based) is Microsoft's browser built on the open-source Chromium/Blink engine, so its security model spans web origins, the same-origin policy, and the browser's own trusted UI (address bar, security indicators, permission prompts). The root cause is classified as CWE-284 Improper Access Control, meaning a resource, origin boundary, or UI surface is reachable or manipulable in a way it should not be. The scope-changed metric (S:C) indicates the flaw in one security authority (for example the renderer or a web origin) affects another (the browser chrome or a different origin), which is the classic pattern behind spoofing where attacker-controlled content is presented as belonging to a trusted context. The affected CPE is cpe:2.3:a:microsoft:microsoft_edge_(chromium-based):*:*:*:*:*:*:*:*, i.e. the application across unspecified versions pending Microsoft's version table.
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
AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N
Network spoofing is unauthenticated (PR:N) but realistically needs victim navigation (UI:R) and is timing-dependent (AC:H); scope changes across origins (S:C) with integrity spoofing high and no genuine availability impact.
Primary rating from Vendor (microsoft).
CVSS VectorNVD
Lifecycle Timeline
3DescriptionNVD
Improper access control in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.
Executive ViewAI
Microsoft Edge contains a high-severity spoofing vulnerability (CVSS 8.1) that allows remote, unauthenticated attackers to manipulate trusted UI elements and deceive users about content origins. While no public exploit has been identified at time of analysis, this vulnerability affects all Edge users in your organization and requires immediate patching to prevent phishing and content-spoofing attacks that could compromise user data and organizational security.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Remote code execution in Microsoft Edge (Chromium-based) before 150.0.4078.48 allows an unauthenticated attacker to run
Security-feature bypass in Microsoft Edge (Chromium-based) versions prior to 150.0.4078.48 lets a remote, unauthenticate
Remote code execution in Microsoft Edge (Chromium-based) lets an attacker run arbitrary code in the browser by getting a
Remote code execution in Microsoft Edge (Chromium-based) before 151.0.4129.59 allows a network attacker to run arbitrary
Remote code execution via buffer over-read in Microsoft Edge (Chromium-based) versions prior to 151.0.4129.59 affects au
Remote code execution in Microsoft Edge (Chromium-based) prior to version 151.0.4129.59 is achievable by an unauthentica
Use-after-free memory corruption in Microsoft Edge (Chromium-based) can let remote attackers execute arbitrary code in t
Remote code execution in Microsoft Edge (Chromium-based) stems from a use-after-free memory corruption flaw (CWE-416) th
Remote code execution in Microsoft Edge (Chromium-based) allows an unauthenticated attacker to run arbitrary code by lur
Remote code execution in Microsoft Edge (Chromium-based) stems from a heap-based buffer overflow (CWE-122) that a networ
Remote code execution in Microsoft Edge (Chromium-based) is enabled by a type confusion vulnerability (CWE-843) that can
Remote code execution in Microsoft Edge (Chromium-based) before version 150.0.4078.48 allows an unauthenticated remote a
EUVD-2026-41584
GHSA-6p36-3w3p-mr82
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB