ChromeWeb browser · Google
CVE-2026-7923
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 write in Skia 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: 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 confidenceAn out-of-bounds write vulnerability exists in Skia (Google's 2D graphics library) within Google Chrome versions prior to 148.0.7778.96. A remote attacker who has already compromised the renderer process can exploit this flaw via a crafted HTML page to potentially escape the browser sandbox and execute code at higher privilege levels.
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 Google Chrome versionOpen Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/helpAffected if The version displayed is lower than 148.0.7778.96
-
Verify Chrome version via command lineOn Windows, check "C:\Program Files\Google\Chrome\Application\chrome.exe" version properties. On macOS, run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --versionAffected if The reported version number is below 148.0.7778.96
-
Check Chrome channel and update statusNavigate to chrome://settings/help and look for the update status message, or check if "Update Chrome" button is present indicating an outdated installationAffected if Chrome reports an update is available or shows a version below 148.0.7778.96
-
Assess renderer compromise riskReview browser extension permissions, disable unnecessary extensions, and verify that JavaScript is restricted on untrusted sites via Chrome's content settingsAffected if The renderer process could be compromised by malicious web content (this flaw is exploitable after initial renderer compromise)
You are affected if your installed Chrome version is below 148.0.7778.96 and an attacker could compromise the renderer process first.
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. In enterprise environments, ensure automated browser update mechanisms or patch management tools are configured to deploy this critical security update across all affected systems.
Chrome 148.0.7778.96 or later
- Open Chrome and navigate to Settings > About Chrome (or enter chrome://version in the address bar) to check the current version
- Click 'Check for updates' or download Chrome version 148.0.7778.96 or later from the official Google Chrome website
- After the update is downloaded, click 'Relaunch' to restart the browser and apply the update
- Verify the update was successful by returning to Settings > About Chrome and confirming the version is 148.0.7778.96 or higher
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-2026-7923 — 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-7923 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