Cyber Resilience

CVE-2025-6191

Memory Safety in Google Chrome ≤ 137.0.7151.119

Memory Safety
Published
18 June 2025
Modified
17 June 2026
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.095 95th percentile
Risk Priority 73 floored blend · peak EPSS

Summary

CVE-2025-6191 is a high-severity External Control of Assumed-Immutable Web Parameter (CWE-472) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A06:2025 Insecure Design

EU & UK References

Vulnerability Data

Integer overflow in V8 in Google Chrome prior to 137.0.7151.119 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)

CWE(s)
CWE-472CWE-190

Related Threats

MITRE ATT&CK Enterprise Techniques

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 →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

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

Affected Assets

google
chrome
≤ 137.0.7151.119

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)
  • V5.2.6

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds integer overflow defects before deployment.

SI-10 Information Input Validation good match

SI-10 directly requires validation of all inputs, eliminating the assumption that client-supplied parameters remain immutable.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer overflow during calculation.

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 server-side validation of all inputs instead of trusting client-supplied immutable parameters.

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
prevents

Secure coding standards require server-side verification of client-supplied data, eliminating the root cause of external control of immutable parameters.

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

Security testing in development and acceptance will detect parameter tampering vulnerabilities before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and integrity checks that directly prevent external tampering of assumed-immutable parameters.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for validation of all inputs, including hidden fields, mitigating CWE-472.

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

Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.

A.8.3 Information access restriction none match
none

Information access restriction can limit which parameters users may influence, providing a secondary layer of defense.

References