Cyber Resilience

CVE-2026-8573

Google Chrome ≤ 148.0.7778.168

Published
14 May 2026
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 8.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS Score 0.0023 14th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

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

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 14th 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-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 Codecs in Google Chrome on Windows prior to 148.0.7778.168 allowed a remote attacker to potentially perform a sandbox escape via a crafted video file. (Chromium security severity: Medium)

CWE(s)
CWE-472

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 →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-7973Same product: Google Chrome
CVE-2026-8510Same product: Google Chrome
CVE-2026-11058Same product: Google Chrome
CVE-2026-8559Same product: Google Chrome
CVE-2026-8567Same product: Google Chrome
CVE-2026-8519Same product: Google Chrome
CVE-2026-9966Same product: Google Chrome
CVE-2025-1915Same product: Google Chrome
CVE-2026-14033Same product: Google Chrome
CVE-2026-7903Same product: Google Chrome

Affected Assets

google
chrome
≤ 148.0.7778.168

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

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

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.3 Information access restriction none match
none

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

References