Cyber Resilience

CVE-2025-1917

Google Chrome ≤ 134.0.6998.35

Published
05 March 2025
Modified
01 April 2025
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
EPSS Score 0.0033 26th percentile
Risk Priority 37 floored blend · peak EPSS

Summary

CVE-2025-1917 is a medium-severity Improper Restriction of Rendered UI Layers or Frames (CWE-1021) vulnerability in Google Chrome. Its CVSS base score is 4.3 (Medium).

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

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

Inappropriate implementation in Browser UI in Google Chrome on Android prior to 134.0.6998.35 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)

CWE(s)
CWE-1021

Related Threats

MITRE ATT&CK Enterprise Techniques

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.
attack.mitre.org →
T1056 Input Capture Collection
Adversaries may use methods of capturing user input to obtain credentials or collect information.
attack.mitre.org →
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-28577Same product: Google Android
CVE-2025-1923Same product: Google Chrome
CVE-2026-0007Same product: Google Android
CVE-2024-31324Same product: Google Android
CVE-2023-20913Same product: Google Android
CVE-2026-0036Same product: Google Android
CVE-2023-7013Same product: Google Chrome
CVE-2026-11127Same product: Google Android
CVE-2024-6995Same product: Google Android
CVE-2024-8907Same product: Google Android

Affected Assets

google
chrome
≤ 134.0.6998.35

Mitigating Controls

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 require implementing frame-ancestors / X-Frame-Options controls that prevent this weakness.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect missing frame protections, but does not itself implement the control.

A.8.23 Web filtering partial match
degrades

Web filtering can block or sandbox untrusted frames, but does not enforce application-level frame-busting or CSP.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate frame-ancestors / X-Frame-Options, directly addressing UI redressing risks.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include isolation of UI layers and proper use of browser security controls.

A.8.28 Secure coding partial match
prevents

Secure coding practices directly require implementation of frame-busting headers or CSP frame-ancestors directives.

References