PatchSiren cyber security CVE debrief
CVE-2026-5874 Google CVE debrief
CVE-2026-5874 is a use-after-free vulnerability in PrivateAI in Google Chrome prior to 147.0.7727.55. An attacker could potentially perform a sandbox escape via a crafted HTML page if a user is convinced to engage in specific UI gestures. This vulnerability has a CVSS score of 9.6, indicating a critical severity level. The vulnerability affects Google Chrome users who have not updated to the latest version. The CVE record and NVD detail page provide further information on the vulnerability.
- Vendor
- Product
- Chrome
- CVSS
- CRITICAL 9.6
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-04-08
- Original CVE updated
- 2026-07-24
- Advisory published
- 2026-04-08
- Advisory updated
- 2026-07-24
Who should care
Users of Google Chrome prior to version 147.0.7727.55 should update to the latest version to mitigate this vulnerability. This vulnerability has a CVSS score of 9.6, indicating a critical severity level. Security teams and administrators responsible for managing Google Chrome deployments should prioritize updating to the latest version.
Technical summary
The vulnerability exists in the PrivateAI component of Google Chrome prior to version 147.0.7727.55. A remote attacker could exploit this vulnerability by convincing a user to engage in specific UI gestures on a crafted HTML page, potentially leading to a sandbox escape. The CVSS vector for this vulnerability is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H. The vulnerability can be mitigated by updating Google Chrome to version 147.0.7727.55 or later.
Defensive priority
High priority should be given to updating Google Chrome to version 147.0.7727.55 or later to mitigate this vulnerability. Security teams should also review compensating controls and monitor for suspicious activity.
Recommended defensive actions
- Update Google Chrome to version 147.0.7727.55 or later
- Ensure that users are aware of the risks associated with engaging in specific UI gestures on untrusted HTML pages
- Monitor for any suspicious activity that could indicate exploitation of this vulnerability
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record for CVE-2026-5874 was published on 2026-04-08T22:16:27.003Z and last modified on 2026-07-24T08:10:00.150Z. The NVD entry is currently Analyzed. However, the information available is limited, and defenders should verify the affected scope and severity with the official CVE record and NVD detail page. The vulnerability exists in Google Chrome prior to version 147.0.7727.55, and users should update to the latest version to mitigate this vulnerability.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-5874 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-5874
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-5874 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-5874
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop.html
[email protected] - Release Notes, Vendor Advisory
-
Source reference
Unverified legacy reference
URL: https://issues.chromium.org/issues/485397279
[email protected] - Permissions Required
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.