Cyber Resilience

CVE-2025-4052

Google Chrome ≤ 136.0.7103.59

Published
05 May 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0057 44th percentile
Risk Priority 72 floored blend · peak EPSS

Summary

CVE-2025-4052 is a critical-severity Inappropriate Encoding for Output Context (CWE-838) vulnerability in Google Chrome. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 44th 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-15 (Information Output Filtering) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Inappropriate implementation in DevTools in Google Chrome prior to 136.0.7103.59 allowed a remote attacker who convinced a user to engage in specific UI gestures to bypass discretionary access control via a crafted HTML page. (Chromium security severity: Low)

CWE(s)
CWE-838

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-3735Same product: Google Chrome
CVE-2026-17717Same product: Google Chrome
CVE-2024-7025Same product: Google Chrome
CVE-2026-16416Same product: Google Chrome
CVE-2026-17705Same product: Google Chrome
CVE-2026-19174Same product: Google Chrome
CVE-2024-9123Same product: Google Chrome
CVE-2026-15108Same product: Google Chrome
CVE-2026-14430Same product: Google Chrome
CVE-2023-0933Same product: Google Chrome

Affected Assets

google
chrome
≤ 136.0.7103.59

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.1
  • V1.2.2
  • V1.2.3
  • V1.2.5

Mitigating Controls (NIST 800-53 r5) AI

SI-15 Information Output Filtering good match

Validates output data representations to ensure consistency with expected formats, directly stopping encoding mismatches for downstream contexts.

SA-8 Security and Privacy Engineering Principles partial match

Requires application of secure engineering principles during development that include correct output encoding for context.

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 correct output encoding to match downstream context, but eliminating only this flaw covers a narrow slice of the broader control.

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.28 Secure coding mostly match
degrades

Secure coding directly addresses proper output encoding for context, covering most of the weakness and the control's intent.

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

Security testing can detect encoding mismatches, but testing alone does not prevent the weakness at source.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle requires encoding-aware output handling, but does not mandate context-specific encoding checks.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify correct output encoding, yet the control is broader than this single weakness.

References