ChromeWeb browser · Google
CVE-2026-9992
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 Network in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to execute arbitrary code inside a sandbox 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 Network component allows a remote attacker to execute arbitrary code via a crafted HTML page. The vulnerability exists prior to version 148.0.7778.216 and operates within the sandbox environment.
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.216< 148.0.7778.215CVSS 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.
-
Determine installed Chrome versionOpen chrome://version in the address bar or go to Menu > Help > About Google ChromeAffected if The displayed version number is lower than 148.0.7778.216 or 148.0.7778.215
-
Verify the exact version stringRecord the full version number shown on the chrome://version page, including the build number (e.g., 148.0.7778.216)Affected if The version is any release prior to 148.0.7778.216 or 148.0.7778.215
-
Confirm Network component exposureThe vulnerability exists in Chrome's Network component used for HTTP/HTTPS requests; any use of web browsing functionality loads this componentAffected if Chrome is used for web browsing and the version is vulnerable, the Network component is automatically exposed to potential attack
-
Check for Chrome updatesGo to Menu > Help > About Google Chrome and verify if updates are available or if the browser reports it is up to dateAffected if The browser reports being out of date or shows a version lower than 148.0.7778.216
If the installed Chrome version is any release prior to 148.0.7778.216 (or 148.0.7778.215), the environment is vulnerable to this use-after-free flaw in the Network component.
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.215148.0.7778.216
Update Google Chrome to version 148.0.7778.216 or later. Deploy browser updates across all affected endpoints using enterprise patch management tools.
Chrome 148.0.7778.216 or later
- 1. Check current Chrome version by navigating to chrome://settings/help or clicking Help > About Google Chrome
- 2. If the installed version is less than 148.0.7778.216, initiate an update by clicking 'Update Google Chrome' button if displayed, or Chrome will automatically update when restarted
- 3. Restart Chrome to complete the update process
- 4. Verify the update was successful by checking the version again; it should show 148.0.7778.216 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9992 — 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-9992 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