ChromeWeb browser · Google
CVE-2026-7967
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 validation of untrusted input in Navigation in Google Chrome prior to 148.0.7778.96 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 · high confidenceInsufficient validation of untrusted input in Chrome's Navigation component allows a remote attacker with a compromised renderer process to potentially escape the sandbox via a crafted HTML page, affecting versions prior to 148.0.7778.96.
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
< 148.0.7778.96CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Check installed Chrome versionNavigate to chrome://settings/help in the Chrome browser, or run 'google-chrome --version' (Linux) or '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' (Windows) in a command promptAffected if The displayed version is less than 148.0.7778.96
-
Confirm Chrome is the affected productEnsure the installed browser is Google Chrome (not Chromium, Edge, or other Chromium-based browsers) - check the browser name in the title bar or via chrome://settingsAffected if The browser is Google Chrome and version is below 148.0.7778.96
-
Verify the attack surface existsThis vulnerability requires a compromised renderer process to be exploitable. Check if the user runs Chrome with the sandbox enabled (default configuration). The vulnerability allows escape FROM an already-compromised renderer, not initial compromise.Affected if Chrome is running with sandbox enabled (default) AND version is below 148.0.7778.96
You are affected if Google Chrome version is below 148.0.7778.96 and the browser is running with default sandbox configuration, as the flaw allows escaping the sandbox from a compromised renderer process.
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 · scoped148.0.7778.96
Update Google Chrome to version 148.0.7778.96 or later through organization-wide patch management, and verify all endpoints have applied the update.
Chrome 148.0.7778.96
- Open Google Chrome browser
- Navigate to Settings > Help > About Google Chrome (or go to chrome://settings/help)
- Chrome will automatically check for updates
- If version 148.0.7778.96 or later is available, click 'Update Google Chrome'
- Restart the browser to apply the update
- Alternatively, download Chrome 148.0.7778.96 or later directly from the official Chrome download page and install over the existing version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7967 — 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-7967 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