CVE-2026-106417: Integer overflow in Media in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to potentially exe

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

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

Q: Is CVE-2026-106417 being exploited?

CVE-2026-106417 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-106417 affect?

CVE-2026-106417 affects chrome. Severity is critical (CVSS 9.6). Integer overflow in Media in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Low)

Q: How urgent is CVE-2026-106417?

Priority 40/100. Critical severity

This month

CRITICAL 9.6UPGRADE

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

Integer overflow in Media in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Low)

Why this priority

Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score	9.6 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 73%)
CISA exploited list	No
Weakness	CWE-190
Published	2026-10-06
Last modified	2026-10-07

Publisher (CNA): Chrome · Vendor: google

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

Am I affected?

Timeline

2026-10-06 19:18 UTCPublished CVE record published
2026-10-07 13:10 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 155.0.8059.39

Fixed in: 155.0.8059.39

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 155.0.8059.39 (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.

Advisories and coverage

Official advisories

Microsoft MSRC Update Guide: Chromium CVE-2026-106417: Integer overflow 2026-10-16

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-106417?

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

Is CVE-2026-106417 being exploited?

CVE-2026-106417 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-106417 affect?

CVE-2026-106417 affects chrome. Severity is critical (CVSS 9.6). Integer overflow in Media in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Low)

How urgent is CVE-2026-106417?

Priority 40/100. Critical severity

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-7898 HIGH 8.8 UPGRADE Use after free in Chromoting in Google Chrome on Linux prior to 148.0.7778.96 allowed a remote attacker to exe
CVE-2026-7951 HIGH 8.8 UPGRADE Out of bounds write in WebRTC in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to execute arb
CVE-2026-7992 HIGH 8.8 UPGRADE Insufficient validation of untrusted input in UI in Google Chrome on Linux, ChromeOS prior to 148.0.7778.96 al
CVE-2026-7902 HIGH 8.8 UPGRADE Out of bounds memory access in V8 in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to execute
CVE-2026-7928 HIGH 8.8 UPGRADE Use after free in WebRTC in Google Chrome on Windows prior to 148.0.7778.96 allowed a remote attacker to execu

References

← Back to latest CVEs