cve.bz

CVE-2025-65046 microsoft edge chromium: Authentication Bypass by Spoofing

3.1 lowEPSS 0.3%

Low (3.1) in microsoft edge chromium. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Microsoft Edge (Chromium-based) Spoofing Vulnerability

Severity

CVSS 3.1

3.1 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-12-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-451 User Interface (UI) Misrepresentation of Critical Information
CWE-290 Authentication Bypass by Spoofing
OWASP Top 10
A06:2025 Insecure Design, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-65046 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-65046?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-65046?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-65046 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-65046

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-65046](https://cve.bz/cve/badge/CVE-2025-65046.svg)](https://cve.bz/cve/CVE-2025-65046)

HTML:

<a href="https://cve.bz/cve/CVE-2025-65046"><img src="https://cve.bz/cve/badge/CVE-2025-65046.svg" alt="CVE-2025-65046"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Edge for Androidfrom 1.0.0 before 143.0.3650.88

Attack patterns (CAPEC)

  • CAPEC-98 Phishing Likelihood: High · Severity: Very High
  • CAPEC-154 Resource Location Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-163 Spear Phishing Likelihood: High · Severity: High
  • CAPEC-164 Mobile Phishing Likelihood: High · Severity: High
  • CAPEC-173 Action Spoofing Likelihood: High · Severity: Very High
  • CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-290.

References

Check your stackJSON