ChromeWeb browser · Google
CVE-2026-7922
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 ServiceWorker in Google Chrome prior to 148.0.7778.96 allowed a remote attacker 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 confidenceA use-after-free vulnerability in Google Chrome's ServiceWorker component allows a remote attacker to escape the browser's sandbox and potentially execute arbitrary code by tricking users into visiting a crafted HTML page. ServiceWorker is a web API that intercepts network requests, and the memory corruption occurs when freed memory is accessed after deallocation.
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 versionNavigate to chrome://settings/help in the Chrome browser, or click Help > About Google Chrome in the menu. The version number is displayed on the page.Affected if The displayed version is lower than 148.0.7778.96 (for example, 148.0.7778.0, 147.x.x.x, etc.)
-
Verify ServiceWorker statusOpen Developer Tools (F12), go to the Application tab, and check the Service Workers section in the left sidebar. Alternatively, navigate to chrome://service-internals/ in the address bar.Affected if ServiceWorker is enabled and registered, meaning the browser uses the affected component.
-
Confirm browser profile usageDetermine if the user accesses untrusted or third-party web content through this Chrome installation. Check for frequent visits to unfamiliar or attacker-controlled websites.Affected if Users routinely visit or can be persuaded to visit malicious HTML pages hosted on untrusted domains.
A user is affected if their Chrome version is below 148.0.7778.96, ServiceWorker is enabled, and they could be tricked into visiting a crafted HTML page.
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 vulnerability. Organizations should enforce browser updates via enterprise management tools and warn users about the risk of visiting untrusted HTML content.
Chrome 148.0.7778.96 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Verify the current version is below 148.0.7778.96
- Click 'Update Google Chrome' if the button is available, or Chrome will automatically check for updates
- Restart Chrome after the update completes
- Confirm the version is now 148.0.7778.96 or later in the About Chrome page
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
- 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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7922 — 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-7922 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