How to Fix CVE-2026-7343: Chrome (Bundle Sibling)
By Sai Kiran Pandrala
Last verified: 2026-05-25
CVE-2026-7343 is a sibling vulnerability in the same vendor advisory as CVE-2026-7333. Applying the patched build named in the primary write-up closes this CVE as well.
| Severity | CVSS 7.5 - High |
|---|---|
| Actively exploited? | Not currently in CISA KEV |
| Affected | Same as the bundle - see CVE-2026-7333 |
| Fixed in | Same patched build as CVE-2026-7333 (See vendor advisory) |
| Type (CWE) | CWE-416: Use after free |
What's different about CVE-2026-7343?
Use after free in Views in Google Chrome on Windows prior to 147.0.7727.138 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.
How to fix CVE-2026-7343
Apply the patched build per the primary write-up: How to Fix CVE-2026-7333.
The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.
Frequently asked questions
Is CVE-2026-7343 fixed by the same patch as CVE-2026-7333?
Yes. CVE-2026-7343 ships in the same vendor advisory as CVE-2026-7333. Applying the patched build named in the primary write-up closes both.
What is the CVSS score for CVE-2026-7343?
The CVSS base score is 7.5 (High).
Is it being exploited?
It is not currently listed in CISA KEV.
References
- Official vendor advisory: https://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop_28.html
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-7343
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary write-up: How to Fix CVE-2026-7333
*Part of the Chrome bundle. Full procedure at CVE-2026-7333.*