How to Fix CVE-2026-3062: Chrome (Bundle Sibling)
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-3062 is a sibling vulnerability in the same vendor advisory as CVE-2026-3061. Apply the same patched build and you close both. The technical detail below is what differs.
| Severity | 8.8 (High) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | Chrome 145.0.7632.116 to <145.0.7632.116 |
| Fixed in | Same patched build as CVE-2026-3061 |
| Type (CWE) | CWE-125 Out-of-bounds Read |
What's different about CVE-2026-3062?
Out of bounds read and write in Tint in Google Chrome on Mac prior to 145.0.7632.116 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)
How to fix CVE-2026-3062
Apply the patched build per the primary write-up: How to Fix CVE-2026-3061. All commands, verification steps, and rollback notes for Chrome are listed there.
Frequently asked questions
Does the CVE-2026-3061 patch close CVE-2026-3062?
Yes. Both CVEs are addressed by the same vendor patch. Applying the patched build closes the full bundle.
Is CVE-2026-3062 listed in CISA KEV?
No public KEV listing at the time of this writing.
Where is the official advisory?
See https://chromereleases.googleblog.com/2026/02/stable-channel-update-for-desktop_23.html
References
- Official vendor advisory: https://chromereleases.googleblog.com/2026/02/stable-channel-update-for-desktop_23.html
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3062
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary: How to Fix CVE-2026-3061
*Written by Sai Kiran Pandrala. Part of the Chrome bundle. Full procedure at how-to-fix-cve-2026-3061.*