465622088253186164: Google Chrome vulnerability
Published Jun 11, 2026
·Updated
Affected Software
1 affected componentFixes available
Google Chrome<149.0.7827.114
149.0.7827.114
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 149.0.7827.114
Event History
Jun 11, 2026
Advisory Published
via Google·12:00 AM
Data Sourced
via Google·12:00 AM
Affected Software
Child vulnerabilities
Contains the following vulnerabilities.
- CVE-2026-12007
- CVE-2026-12008
- CVE-2026-12009
- CVE-2026-12010
- CVE-2026-12011
- CVE-2026-12012
- CVE-2026-12014
- CVE-2026-12015
- CVE-2026-12016
- CVE-2026-12017
- CVE-2026-12018
- CVE-2026-12019
- CVE-2026-12020
- CVE-2026-12022
- CVE-2026-12023
- CVE-2026-12024
- CVE-2026-12025
- CVE-2026-12026
- CVE-2026-12027
- CVE-2026-12028
- CVE-2026-12029
- CVE-2026-12030
- CVE-2026-12031
- CVE-2026-12032
- CVE-2026-12033
- CVE-2026-12034
- CVE-2026-12035
Frequently Asked Questions
1
What is the severity of vulnerability 465622088253186164?
The severity of vulnerability 465622088253186164 is classified as high.
2
How do I fix vulnerability 465622088253186164?
To fix vulnerability 465622088253186164, update Google Chrome to the latest version immediately.
3
What versions of Google Chrome are affected by vulnerability 465622088253186164?
Vulnerability 465622088253186164 affects multiple versions prior to the latest release of Google Chrome.
4
What types of attacks can exploit vulnerability 465622088253186164?
Vulnerability 465622088253186164 can potentially be exploited through remote code execution attacks.
5
Is there a workaround for vulnerability 465622088253186164?
There are no known workarounds for vulnerability 465622088253186164; updating is the only effective solution.