ChromeWeb browser · Google
CVE-2026-9122
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 · uneditedOut of bounds read in GPU in Google Chrome on Mac prior to 148.0.7778.179 allowed a remote attacker to obtain potentially sensitive information from process memory 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 confidenceOut of bounds read vulnerability in Google Chrome's GPU rendering component on macOS allows a remote attacker to access process memory beyond allocated buffers via a malicious HTML page, potentially exposing sensitive data.
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.179CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 Chrome is installed on macOSOpen Terminal and run: ls /Applications/Google\ Chrome.app or check /Applications folder for Google ChromeAffected if Google Chrome.app does not exist in /Applications - not affected if Chrome is not installed
-
Check installed Chrome version on macOSOpen Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version OR open Chrome, click Chrome menu > About Google ChromeAffected if Version displayed is less than 148.0.7778.179 - vulnerable version range
-
Confirm GPU rendering feature is enabledOpen Chrome, navigate to chrome://settings/?search=GPU, or check chrome://gpu/ page to verify GPU compositing is in useAffected if GPU rendering is enabled - this is the attack surface for the vulnerability
-
Verify macOS platformRun 'uname -a' in Terminal or click Apple menu > About This Mac to confirm macOSAffected if System is running macOS - this CVE specifically affects the macOS GPU rendering component
User is affected if Chrome is installed on macOS AND version is below 148.0.7778.179 AND GPU rendering is enabled (default behavior)
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.179
Update Google Chrome for Mac to version 148.0.7778.179 or later to patch the GPU out-of-bounds read vulnerability.
Chrome 148.0.7778.179 (or later stable release)
- Open Google Chrome on Mac
- Click on the Chrome menu (three-dot menu) in the top-right corner
- Select 'Help' and then 'About Google Chrome'
- Chrome will check for updates automatically
- If update to version 148.0.7778.179 or later is available, click 'Update Google Chrome'
- Restart the browser to complete the installation
- After restart, verify the version by returning to About Google Chrome and confirming the version number is 148.0.7778.179 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-9122 — 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-9122 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