Skip to main content
VulnerabilityPublished Updated

CVE-2025-49713: Microsoft Edge (Chromium-based) · Type Confusion

Affects Microsoft Edge (Chromium-based)Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
NuGetmicrosoft-edgepkg:nuget/microsoft-edgeOther threatsAffected
  • =1.0.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-49713 effectively, organizations should implement a multi-layered approach beyond generic advice. First, restrict or disable Microsoft Edge usage in sensitive or high-risk environments until a security patch is released. Employ application control policies to limit execution of untrusted or unknown code initiated via the browser. Enable advanced browser security features such as sandboxing, strict site isolation, and enhanced memory protection mechanisms if configurable. Deploy network-level protections including web filtering to block access to suspicious or untrusted websites. Monitor endpoint behavior for indicators of exploitation such as unusual process spawning or memory anomalies related to Edge. Educate users to avoid clicking on unknown links or opening untrusted attachments that could trigger the vulnerability. Maintain up-to-date backups and incident response plans in case of compromise. Once Microsoft releases a patch, prioritize rapid deployment across all affected systems. Additionally, consider using alternative browsers with a lower risk profile temporarily if feasible. Continuous threat intelligence monitoring for exploit developments is also recommended.

Description

Access of resource using incompatible type ('type confusion') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.

References

Community reviews

Loading reviews…