ChromeWeb browser · Google

CVE-2026-7992

HIGH · 8.8 CVSS v3.1 Published 2026-05-06

Fix available

A fix is available. Upgrade to 148.0.7778.96 or later.

See remediation →

95/100

Remediation priority · Urgent

Remotely reachable No privileges

Official description

NVD · unedited

Insufficient validation of untrusted input in UI in Google Chrome on Linux, ChromeOS prior to 148.0.7778.96 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code via a crafted HTML page. (Chromium security severity: Medium)

Technical summary

dbcve analysis · moderate confidence

Insufficient validation of untrusted input in Google Chrome's UI component on Linux and ChromeOS allows a remote attacker to execute arbitrary code via crafted HTML pages when users perform specific UI gestures. The vulnerability exists due to missing input validation in the UI rendering pipeline prior to version 148.0.7778.96.

MitigationUpdate Google Chrome to version 148.0.7778.96 or later on all Linux and ChromeOS systems to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 148.0.7778.96

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify Google Chrome is installed

Check for Chrome executable: run 'which google-chrome' or 'which chrome' on Linux/ChromeOS systems. Alternatively, look for Chrome in /usr/bin/google-chrome or ~/.local/bin/

Affected if Chrome browser is not found on the system (not affected)
Determine the installed Chrome version

Run 'google-chrome --version' or 'google-chrome -version' in the terminal to retrieve the installed version number

Affected if Command fails or returns no version (Chrome not properly installed)
Confirm the operating system is Linux or ChromeOS

Run 'uname -a' or check /etc/os-release to identify the OS. This vulnerability only affects Linux and ChromeOS, not Windows or macOS

Affected if OS is Windows or macOS (not affected by this specific CVE)
Compare installed version against vulnerable range

Take the version number from step 2 (e.g., 148.0.7778.96) and compare it against the affected range: any version prior to 148.0.7778.96 is vulnerable

Affected if Installed version is lower than 148.0.7778.96 (e.g., 147.x.x.x, 146.x.x.x)

The system is affected if Google Chrome is installed on Linux or ChromeOS with a version number lower than 148.0.7778.96

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 148.0.7778.96 or later

Fixed in 148.0.7778.96

Interim mitigation

Update Google Chrome to version 148.0.7778.96 or later on all Linux and ChromeOS systems to remediate this vulnerability.

Recommended fix High confidence

Chrome version 148.0.7778.96 or later

Open Google Chrome on your Linux or ChromeOS system
Click the three-dot menu icon in the top-right corner
Select 'Help' from the dropdown menu
Click 'About Google Chrome'
Chrome will automatically check for and download available updates
If version 148.0.7778.96 or later is available, click 'Update Google Chrome'
Restart Chrome completely to apply the update
After restart, verify the version by returning to About Google Chrome to confirm the installed version

Caveat Chrome updates are generally seamless with no breaking changes for end users; ensure all extensions are compatible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory

Consultation2.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

7.0 hours of engineering $1,240

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-7992 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

chromereleases.googleblog.comVendor Advisory
issues.chromium.orgIssue TrackingPermissions Required
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7992 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-7992?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsUpgrade to 148.0.7778.96 or later

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Chrome

Remediation

A high-priority fix

Fix this in Chrome 7 hrs · Low

Typical engagement from $1,240

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-7992 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

CVSS 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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References