CVE-2025-47967VulnerabilityPublished 16 Sep 2025Updated 20 Feb 2026

CVE-2025-47967: Microsoft Edge (Chromium-based) · Insufficient UI Warning of Dangerous Operations

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

Not known to be exploited · CVSS 4.7 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% 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:C/C:N/I:L/A:N/E:U/RL:O/RC:C

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: None

Temporal metrics

Exploit Code Maturity: Unproven
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Unproven: No exploit code is available, or an exploit is theoretical.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Sep 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

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

AI-suggested

To mitigate CVE-2025-47967, organizations should prioritize the following actions: 1) Monitor Microsoft’s security advisories closely for patches or updates addressing this vulnerability and apply them promptly once available. 2) Educate users about the risks of interacting with suspicious UI elements, especially when connected to untrusted networks such as public Wi-Fi. 3) Implement network security controls such as VPNs or secure Wi-Fi to reduce exposure to network-based spoofing attacks. 4) Employ mobile device management (MDM) solutions to enforce browser update policies and restrict installation of unapproved applications. 5) Consider deploying additional endpoint protection tools that can detect anomalous browser behavior or UI spoofing attempts. 6) Conduct regular security awareness training emphasizing the importance of verifying UI authenticity and avoiding risky interactions. 7) For critical environments, evaluate alternative browsers with stronger UI security or sandboxing features until a patch is available. These measures collectively reduce the attack surface and user susceptibility to spoofing attacks stemming from this vulnerability.

Description

Insufficient ui warning of dangerous operations in Microsoft Edge for Android allows an unauthorized attacker to perform spoofing over a network.

Impact

The primary impact of CVE-2025-47967 is on the integrity of user interactions within Microsoft Edge on Android. By enabling spoofing attacks, malicious actors can deceive users into believing they are interacting with legitimate UI elements when they are not, potentially leading to unauthorized actions or data manipulation. Although confidentiality and availability are not directly affected, the loss of trust in UI integrity can facilitate phishing, social engineering, or other secondary attacks that compromise user security. Organizations relying on Microsoft Edge for Android in their mobile workforce or customer-facing applications may face increased risk of fraud or data integrity issues. The vulnerability's exploitation requires user interaction but no privileges, making it accessible to a wide range of attackers, especially in hostile network environments. Given the widespread use of Android devices and Microsoft Edge, the scope of affected systems is significant, particularly in sectors with high mobile usage such as finance, healthcare, and government. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future attacks.

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2025-47967 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Feb 2026, 21:14 UTC

WeaknessesCWE-357

Technical details

References

Community reviews

Related threats