CVE-2025-21404: Microsoft Edge (Chromium-based) · The UI Performs the Wrong Action
Affects Microsoft Edge (Chromium-based)Source CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 64% 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:N/I:L/A:N/E:U/RL:O/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 6 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Microsoft Edge (Chromium-based) | Affected
| Fixed in– |
AI-suggested
- Immediately audit and inventory all Microsoft Edge installations to identify any running the affected version 1.0.0.0 and prioritize their upgrade or replacement.
- Until a patch is released, restrict the use of the vulnerable Edge version through application control policies or endpoint management solutions.
- Enhance user awareness training focused on recognizing suspicious UI behavior and phishing attempts, emphasizing caution with unexpected browser prompts or actions.
- Implement multi-factor authentication (MFA) on critical systems to reduce the impact of potential credential theft resulting from spoofing attacks.
- Monitor network traffic and endpoint logs for unusual browser behavior or user actions that could indicate exploitation attempts.
- Coordinate with Microsoft for timely updates and apply patches as soon as they become available.
- Consider deploying browser security extensions or tools that can detect or block UI spoofing or phishing attempts.
- For high-risk environments, consider temporarily using alternative browsers until the vulnerability is addressed.
- Integrate this vulnerability into incident response playbooks to ensure rapid detection and response if exploitation is suspected.
Description
Microsoft Edge (Chromium-based) Spoofing Vulnerability