Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-113018: Memory corruption in IME in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially exec

40
This month
HIGH 8.8UPGRADE

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

Memory corruption in IME in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance0.4% (top 63%)
CISA exploited listNo
WeaknessCWE-119
Published2026-10-20
Last modified2026-10-22
Publisher (CNA): Chrome · Vendor: google

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

google chrome UPGRADE
Affected: < 156.0.8078.47
Fixed in: 156.0.8078.47
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy chrome || rpm -q chrome || chrome --version
2. UPGRADE to 156.0.8078.47 (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.

Exact fixes by distribution

Fedora 46 · retext · FIXED · 8.1.0-1.fc46 · FEDORA-2026-0602a84203 · source
sudo dnf upgrade --advisory=FEDORA-2026-0602a84203
Ubuntu 22.04 · chromium-browser · NOT AFFECTED
Ubuntu 24.04 · chromium-browser · NOT AFFECTED
Debian 12 · chromium · FIXED · 156.0.8078.47-1~deb12u1
sudo apt update && sudo apt install --only-upgrade chromium dpkg --compare-versions "$(dpkg-query -W -f='${Version}' chromium)" ge "156.0.8078.47-1~deb12u1" && echo PATCHED || echo STILL-VULNERABLE
Debian 13 · chromium · FIXED · 156.0.8078.47-1~deb13u1
sudo apt update && sudo apt install --only-upgrade chromium dpkg --compare-versions "$(dpkg-query -W -f='${Version}' chromium)" ge "156.0.8078.47-1~deb13u1" && echo PATCHED || echo STILL-VULNERABLE
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-113018?

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

Is CVE-2026-113018 being exploited?

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

CVE-2026-113018 affects chrome. Severity is high (CVSS 8.8). Memory corruption in IME in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

How urgent is CVE-2026-113018?

Priority 40/100. High severity

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.