Skip to main content
Mallory
High

Remote Code Execution in Microsoft Edge (Chromium-based) Type Confusion

IdentifiersCVE-2025-49713CWE-843· Access of Resource Using…

CVE-2025-49713 is a remote code execution vulnerability in Chromium-based Microsoft Edge caused by type confusion, classified as CWE-843 (Access of Resource Using Incompatible Type). Microsoft describes the issue as allowing an unauthorized attacker to execute code over a network. The available supporting content indicates the flaw can be triggered when a user is induced to visit attacker-controlled content, such as a specially crafted website or malicious link. Additional reporting attributes the bug to the browser’s V8 JavaScript engine, but that detail is not consistently corroborated across the provided sources and should therefore be treated with caution. Microsoft fixed the issue in Edge version 138.0.3351.65.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote code execution in the context of Microsoft Edge. Based on the provided CVSS vector and Microsoft’s description, the vulnerability can have high confidentiality, integrity, and availability impact. An attacker who successfully exploits the flaw could run arbitrary code within the browser context and potentially use that access to further compromise user data or system integrity, subject to browser sandboxing and any subsequent post-exploitation constraints.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by limiting users’ ability to access untrusted websites, blocking malicious links and attachments through email and web filtering, and reinforcing phishing-resistant user workflows. Because exploitation requires user interaction, mitigations should focus on preventing users from opening attacker-controlled content. Enterprise defenders should also monitor for outdated Edge versions and enforce rapid browser update compliance. No vendor-specific workaround beyond applying the official fix was provided in the supplied content.

Remediation

Patch, then assume compromise.

Apply the vendor fix by updating Microsoft Edge (Chromium-based) to version 138.0.3351.65 or later. The provided content states that Microsoft released the fix on July 1, 2025, and that Edge 138.0.3351.65 is based on Chromium 138.0.7204.96/.97. Standard remediation is to ensure all affected Edge installations are updated to the patched build through enterprise software deployment, browser auto-update validation, or manual update where necessary.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationEdge Chromiumapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.