ChromeWeb browser · Google
CVE-2026-7998
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 Dialog in Google Chrome prior to 148.0.7778.96 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)
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 Google Chrome's Dialog component allows a remote attacker who has already compromised the renderer process to perform UI spoofing via a crafted HTML page. The vulnerability exists in Chrome 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
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 Chrome versionNavigate to chrome://version in the Chrome browser address bar and note the full version number displayedAffected if The version number is less than 148.0.7778.96 (e.g., 148.0.7778.0, 147.x.x.x, etc.)
-
Verify version via about dialogClick the three-dot menu > Help > About Google Chrome to view the current version and compare against the affected rangeAffected if The displayed version shows a build number below 148.0.7778.96
-
Check for Dialog element usageInspect any web pages or web applications that use the HTML <dialog> element, as the vulnerability is in the Dialog component handlingAffected if The Dialog element is present and rendered in the browser context while running an affected version
-
Confirm renderer process integrityReview browser extensions and any running processes for signs of compromise, as the attacker must already control the renderer process to exploit this flawAffected if Suspicious extensions are installed or renderer process shows unexpected behavior combined with an affected Chrome version
If Chrome version is below 148.0.7778.96 and the Dialog component is being used in web content, the environment is vulnerable to UI spoofing attacks.
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 remediate this vulnerability. Users should ensure their browsers are patched through normal update mechanisms.
Chrome 148.0.7778.96 or later
- 1. Open Google Chrome browser
- 2. Click the three-dot menu icon in the upper-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
- 6. Click 'Relaunch' or 'Restart' to apply the update
- 7. Verify the update 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
- 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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7998 — 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-7998 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