CVE-2026-7950: Out of bounds read and write in GFX in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to perfo

Q: How do I fix CVE-2026-7950?

chrome: upgrade to 148.0.7778.96. Exact commands for each OS are on this page.

Q: Is CVE-2026-7950 being exploited?

CVE-2026-7950 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-7950 affect?

CVE-2026-7950 affects chrome. Severity is medium (CVSS 5.4). Out 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)

Q: How urgent is CVE-2026-7950?

Priority 21/100. No elevated risk signals yet.

Routine

MEDIUM 5.4UPGRADE

CVE-2026-7950 is a medium-severity flaw (CVSS 5.4) affecting chrome. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Out 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)

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 94%)
CISA exploited list	No
Weakness	CWE-125, CWE-787
Published	2026-05-06
Last modified	2026-10-25

Publisher (CNA): Chrome · Vendor: google

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-06 19:16 UTCPublished CVE record published
2026-10-25 23:10 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 148.0.7778.96

Fixed in: 148.0.7778.96

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy chrome || rpm -q chrome || chrome --version

2. UPGRADE to 148.0.7778.96 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade chrome

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade chrome

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-7950?

chrome: upgrade to 148.0.7778.96. Exact commands for each OS are on this page.

Is CVE-2026-7950 being exploited?

CVE-2026-7950 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-7950 affect?

CVE-2026-7950 affects chrome. Severity is medium (CVSS 5.4). Out 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)

How urgent is CVE-2026-7950?

Priority 21/100. No elevated risk signals yet.

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-6299 HIGH 8.8 UPGRADE Use after free in Prerender in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to execute arbi
CVE-2026-6300 HIGH 8.8 UPGRADE Use after free in CSS in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to execute arbitrary
CVE-2026-6307 HIGH 8.8 UPGRADE Type Confusion in Turbofan in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to execute arbit
CVE-2026-8018 HIGH 8.1 UPGRADE Insufficient policy enforcement in DevTools in Google Chrome prior to 148.0.7778.96 allowed a remote attacker
CVE-2026-8016 HIGH 8.8 UPGRADE Use after free in WebRTC in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to execute arbitrar

References

← Back to latest CVEs