ChromeWeb browser · Google
CVE-2025-3066
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 · uneditedUse after free in Site Isolation in Google Chrome prior to 135.0.7049.84 allowed a remote attacker to potentially exploit heap corruption 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 · high confidenceUse-after-free vulnerability in Chrome's Site Isolation feature allows a remote attacker to exploit heap corruption by tricking users into visiting a crafted HTML page. The flaw occurs when memory is accessed after being freed, potentially enabling arbitrary code execution.
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
< 135.0.7049.52CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Check installed Chrome versionNavigate to chrome://version in the browser address bar, or run 'google-chrome --version' from command line, or on Windows check the version property of chrome.exe in Program FilesAffected if The displayed version is lower than 135.0.7049.52
-
Confirm Site Isolation is enabledNavigate to chrome://flags/#enable-site-per-process and check if the flag is set to Enabled, or check the SiteIsolationGroupPolicy in Windows Group Policy Editor under Computer Configuration > Administrative Templates > Google Chrome > Site IsolationAffected if Site Isolation is enabled (this is the feature where the vulnerability exists)
-
Verify the combination of version and featureCross-reference the detected Chrome version against the affected range and confirm Site Isolation statusAffected if Chrome version is below 135.0.7049.52 AND Site Isolation feature is enabled in the browser
You are affected if your installed Google Chrome version is lower than 135.0.7049.52 and the Site Isolation feature is active in your browser.
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 · scoped135.0.7049.52
Update Google Chrome to version 135.0.7049.84 or later. Organizations should deploy browser updates through their patch management systems and verify complete coverage across all endpoints.
Chrome 135.0.7049.84 or later
- Open Google Chrome browser
- Navigate to Settings > About Chrome (or go to chrome://settings/help)
- Chrome will automatically check for updates
- If version 135.0.7049.84 or later is available, click 'Update Google Chrome'
- Restart the browser to apply the security update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3066 — 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-2025-3066 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