How to Fix CVE-2026-3545: Chrome (Bundle Sibling)
By Sai Kiran Pandrala. Last verified: 2026-05-25.
CVE-2026-3545 is a sibling vulnerability in the same vendor advisory as CVE-2026-3536. Apply the same patched build and you close both. The technical detail below is what differs.
| Severity | 9.6 (Critical) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | Chrome 145.0.7632.159 to <145.0.7632.159 |
| Fixed in | Same patched build as CVE-2026-3536 |
| Type (CWE) | CWE-20 Improper Input Validation |
What's different about CVE-2026-3545?
Insufficient data validation in Navigation in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
How to fix CVE-2026-3545
Apply the patched build per the primary write-up: How to Fix CVE-2026-3536. All commands, verification steps, and rollback notes for Chrome are listed there.
Frequently asked questions
Does the CVE-2026-3536 patch close CVE-2026-3545?
Yes. Both CVEs are addressed by the same vendor patch. Applying the patched build closes the full bundle.
Is CVE-2026-3545 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/03/stable-channel-update-for-desktop.html
References
- Official vendor advisory: https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop.html
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3545
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Primary: How to Fix CVE-2026-3536
*Written by Sai Kiran Pandrala. Part of the Chrome bundle. Full procedure at how-to-fix-cve-2026-3536.*