Skip to main content
CVE-2025-21408VulnerabilityPublished Updated

CVE-2025-21408: 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 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.3% chance of exploitation in 30 days – higher than 70% 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 6 Feb 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Microsoft Microsoft Edge (Chromium-based)Affected
  • =1.0.0.0
Fixed in–

AI-suggested

1. Monitor Microsoft security advisories closely and apply official patches immediately upon release. 2. Until patches are available, restrict or disable Microsoft Edge usage on critical systems where possible. 3. Implement strict browser security policies such as disabling JavaScript or using browser isolation technologies for untrusted sites. 4. Educate users about phishing and social engineering risks to reduce likelihood of triggering the exploit. 5. Employ network-level protections such as web filtering and intrusion detection systems to block access to known malicious URLs. 6. Use endpoint detection and response (EDR) tools to monitor for anomalous browser behavior indicative of exploitation attempts. 7. Consider deploying application control or whitelisting to prevent execution of unauthorized code. 8. Regularly audit and update browser versions across the organization to minimize exposure to known vulnerabilities. 9. Coordinate with IT and security teams to prepare incident response plans specific to browser-based remote code execution attacks. 10. Evaluate alternative browsers temporarily if patching is delayed and operationally feasible.

Description

Microsoft Edge (Chromium-based) Remote Code Execution Vulnerability

References

Community reviews

Loading reviews…