Cyber Resilience

CVE-2025-9865

Google Chrome ≤ 140.0.7339.80

Published
03 September 2025
Modified
17 June 2026
CVSS Score v3.1 5.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
EPSS Score 0.0025 16th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-9865 is a medium-severity User Interface (UI) Misrepresentation of Critical Information (CWE-451) vulnerability in Google Chrome. Its CVSS base score is 5.4 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-2 (Flaw Remediation) and SC-18 (Mobile Code) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Inappropriate implementation in Toolbar in Google Chrome on Android prior to 140.0.7339.80 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform domain spoofing via a crafted HTML page. (Chromium security severity: Medium)

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
Why these techniques?

Domain spoofing via crafted HTML page in browser directly enables drive-by compromise through UI misrepresentation.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-10984Same product: Google Android
CVE-2026-13987Same product: Google Android
CVE-2026-13994Same product: Google Android
CVE-2026-13964Same product: Google Android
CVE-2025-12729Same product: Google Android
CVE-2023-0130Same product: Google Android
CVE-2026-11175Same product: Google Android
CVE-2026-11270Same product: Google Android
CVE-2026-13996Same product: Google Chrome
CVE-2026-13966Same product: Google Chrome

Affected Assets

google
chrome
≤ 140.0.7339.80

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • SI-10 Information Input Validation
  • SC-18 Mobile Code
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly addresses the inappropriate Toolbar implementation by requiring prompt application of the vendor fix that eliminates the domain-spoofing flaw.

prevent

Validates untrusted HTML input and UI rendering to block crafted pages that exploit the Toolbar misrepresentation weakness.

SC-18 Mobile Code partial match
prevent

Restricts and sanitizes mobile code (web content) execution on Android to reduce the attack surface for UI-based domain spoofing.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly address design and implementation of accurate, non-spoofable UI elements.

PR.AT-01 partial match
prevents

User awareness training helps people recognize and avoid harm from UI misrepresentation such as phishing, but does not prevent the flaw itself.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect UI misrepresentation vulnerabilities before deployment.

prevents

Security awareness training can teach users to recognize UI misrepresentation and phishing attempts.

mitigates

Web filtering can block known phishing sites that exploit UI misrepresentation.

prevents

Secure development lifecycle includes UI/UX security requirements that can prevent misrepresentation of critical information.

prevents

Application security requirements can mandate proper display and validation of critical information in the UI.

prevents

Secure coding practices can prevent UI flaws that obscure or spoof critical information.

References