ChromeWeb browser · Google
CVE-2026-7950
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 and write in GFX in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to perform arbitrary read/write via malicious network traffic. (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 · moderate confidenceThis is a memory safety vulnerability in Google Chrome's GFX (graphics) component where an out-of-bounds read/write flaw allows a remote attacker to perform arbitrary memory read/write operations via malicious network traffic.
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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 Google Chrome is installedCheck for Chrome installation - on Windows look in Program Files/Google/Chrome/Application/, on macOS in /Applications/, or run 'chrome --version' or check chrome://version in the browserAffected if Chrome is found to be installed on the system
-
Determine installed Chrome versionNavigate to chrome://version in the Chrome browser or run 'chrome --version' from command line to obtain the full version stringAffected if The displayed version is any build earlier than 148.0.7778.96
-
Compare version against affected rangeParse the installed version number and compare numerically against 148.0.7778.96 - the first three octets (148.0.7778) must be compared, then the build number (96)Affected if The installed version falls below 148.0.7778.96 in any component of the version string
-
Confirm GFX component is in useThis vulnerability affects the GFX graphics component which is always active when Chrome renders any visual content - no additional configuration check needed as the component cannot be disabledAffected if Chrome is being used to render any web content or local pages, which activates the GFX component
The environment is affected if Google Chrome is installed and the running version is numerically lower than 148.0.7778.96 in any version 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.96
Update Google Chrome to version 148.0.7778.96 or later to patch the vulnerability. Organizations should ensure browser update policies are enforced across all endpoints.
Chrome 148.0.7778.96 or later
- Update Google Chrome to version 148.0.7778.96 or later
- To update: Open Chrome, go to Menu > Help > About Google Chrome, or navigate to chrome://settings/help
- Chrome will automatically check for updates and prompt you to restart after installing the update
- Verify the installed 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
- 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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7950 — 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-7950 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