ChromeWeb browser · Google
CVE-2026-7938
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 CSS in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to execute arbitrary code inside a sandbox 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 confidenceUse-after-free vulnerability in the CSS rendering component of Google Chrome versions prior to 148.0.7778.96 allows a remote attacker to execute arbitrary code via a malicious crafted HTML page. Although the code executes within a sandbox, the CVSS score of 8.8 indicates successful exploitation can achieve code execution beyond the sandbox's isolation.
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
- 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.
-
Verify Google Chrome is installedOpen terminal or command prompt and run: chrome --version (Windows) or google-chrome --version (Linux) or check /Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version (macOS)Affected if Chrome is installed on the system
-
Determine installed Chrome versionNavigate to chrome://settings/help in the Chrome browser, or run the version command from step 1Affected if Version number displayed is less than 148.0.7778.96
-
Confirm CSS rendering is enabledThe vulnerability exists in Chrome's CSS parsing engine, which is a core built-in feature. No additional configuration check is needed as CSS handling is always active in normal Chrome usageAffected if Chrome is being used for web browsing with any CSS-based content
User is affected if Google Chrome version is installed and is lower than 148.0.7778.96, as the use-after-free vulnerability in CSS parsing exists in all prior versions.
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 to patch the CSS use-after-free vulnerability.
Google Chrome 148.0.7778.96 or later (stable channel)
- 1. Open Google Chrome on the affected system
- 2. Click the three-dot menu icon in the top-right corner
- 3. Select 'Help' from the dropdown menu
- 4. Click 'About Google Chrome'
- 5. Chrome will automatically check for updates and download version 148.0.7778.96 or later if not already on that version
- 6. Click 'Relaunch' or restart the browser manually to apply the update
- 7. Verify the version by returning to About Google 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
- 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-7938 — 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-7938 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