ChromeWeb browser · Google
CVE-2026-3926
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 · uneditedOut of bounds read in V8 in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: Medium)
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 confidenceOut of bounds read vulnerability in the V8 JavaScript engine in Google Chrome prior to version 146.0.7680.71 allows a remote attacker to perform out-of-bounds memory access via a crafted HTML page, potentially enabling information disclosure or辅助 exploitation.
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
< 146.0.7680.71CVSS 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 Chrome version in browserOpen Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on this page.Affected if The displayed version is less than 146.0.7680.71
-
Check Chrome version via command lineRun 'google-chrome --version' on Linux, 'C:\Program Files\Google\Chrome\Application\chrome.exe --version' on Windows, or 'Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' on macOS.Affected if The reported version number is less than 146.0.7680.71
-
Verify V8 engine is presentThe V8 engine is built into Chrome and cannot be disabled. This check confirms Chrome's JavaScript processing capability is active.Affected if Chrome is installed and functional - the V8 engine is always enabled by default.
-
Confirm browser can access web contentThe vulnerability is triggered by loading a crafted HTML page in Chrome. Verify if the browser can navigate to arbitrary websites.Affected if The browser has network access and can render HTML pages - this is the default Chrome behavior.
If the installed Chrome version is below 146.0.7680.71 and the browser can render HTML pages, the environment is affected by this V8 out-of-bounds read vulnerability.
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 · scoped146.0.7680.71
Update Google Chrome to version 146.0.7680.71 or later to patch the V8 engine vulnerability.
Chrome 146.0.7680.71 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- The browser will automatically check for and download the latest version
- Restart Chrome to complete the installation of version 146.0.7680.71 or later
- Verify the version by returning to Settings > Help > About Google Chrome and confirming the version is 146.0.7680.71 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3926 — 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-3926 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