ChromeWeb browser · Google
CVE-2026-3545
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficient 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)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceInsufficient data validation in the Navigation component of Google Chrome prior to version 145.0.7632.159 allows a remote attacker to potentially escape the browser sandbox via a specially crafted HTML page, leading to arbitrary code execution or further system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 145.0.7632.159< 145.0.7632.160CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Google Chrome is installedOpen chrome://version in the address bar or go to Help > About Google Chrome. Note the product name listed.Affected if The product name is Google Chrome (not Chromium or another browser)
-
Identify the installed Chrome versionOn the chrome://version page or About Chrome page, locate the version number displayed (e.g., 145.0.7632.120).Affected if A version number is present showing Google Chrome is installed
-
Compare version against vulnerable rangeCompare your installed version number to the affected range: versions below 145.0.7632.159 or 145.0.7632.160 are vulnerable. Note: if your version is 145.0.7632.159 or higher, you are not affected.Affected if Installed version is less than 145.0.7632.159 (or less than 145.0.7632.160 depending on which version boundary applies)
If Google Chrome is installed and the version is below 145.0.7632.159, the browser is vulnerable to the navigation component sandbox escape.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped145.0.7632.159145.0.7632.160
Update Google Chrome to version 145.0.7632.159 or later to remediate the navigation data validation vulnerability. Organizations should also ensure browser sandboxing settings remain enabled.
Google Chrome 145.0.7632.159 or later
- 1. Open Google Chrome and navigate to Help > About Google Chrome to check the current version number
- 2. If the installed version is below 145.0.7632.159, download the latest stable Chrome version from the official Google Chrome download page (chrome.com) or wait for automatic update
- 3. Install the updated Chrome version
- 4. Restart the browser if prompted
- 5. Verify the version has been updated to 145.0.7632.159 or higher by returning to Help > About Google Chrome
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3545 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3545 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data