Patch Forecast
Yellow warning
Plan into this sprint.

CVE-2026-113122

Chrome: memory corruption

Risk score
43/100
CVSS
6.5 v3.1
Exploit chance (30 days)
0.3%
Published
20 Oct 2026

Open in the live forecast Today's forecast

What to know

What it is
Memory corruption in Loader in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Low)
Affected
Chrome before 156.0.8078.47
Fix
Upgrade Chrome to 156.0.8078.47 or later.
Exploitation
No known exploitation

Story map

Story map: ChromeTHE FLAWSTHE FIXCVE-2026-113122Memory corruptionCVSS 6.5 · EPSS 0%CVE-2026-106329Incorrect authorisation canlead to remote code executionCVSS 9.6 · EPSS 0%CVE-2026-106417Integer overflow can lead toremote code executionCVSS 9.6 · EPSS 0%CVE-2026-110136Use-after-free can lead toremote code executionCVSS 9.6 · EPSS 0%Upgrade Chrome156.0.8078.47 · 155.0.8059.39· 155.0.8059.79or later on your release lineWho is exposedChrome before 155.0.8059.39AMBER · PATCH THIS WEEKChromeIncorrect authorization inFileSystem in Google Chromeprior to 155.0.8059.39 allowed aremote attacker leveragingsocial engineering to potentiallyexecute arbitrary code outsidethe sandbox via a crafted HTML…Where it standsNo known exploitationHOW IT UNFOLDEDOfficial record on the left, the press on the right, oldest first.16 Oct · Microsoft Security Response CenterChromium CVE-2026-106329: Incorrectauthorization16 Oct · Microsoft Security Response CenterChromium CVE-2026-106417: Integer overflow16 Oct · Microsoft Security Response CenterChromium CVE-2026-110136: Use after freeCONNECTS TOSame weaknessMemory corruption (CWE-119)271 other warnings in 30 days →Same productEarlier Chrome warnings397 in the last 90 days →
Story map: the flaws, the fix, how it unfolded and what it connects to. Boxes link to the record or article.

At a glance

Chrome: Amber, patch this week. Incorrect authorization in FileSystem in Google Chrome prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

The flaws

  • CVE-2026-113122: Memory corruption (CVSS 6.5 · EPSS 0%)
  • CVE-2026-106329: Incorrect authorisation can lead to remote code execution (CVSS 9.6 · EPSS 0%)
  • CVE-2026-106417: Integer overflow can lead to remote code execution (CVSS 9.6 · EPSS 0%)
  • CVE-2026-110136: Use-after-free can lead to remote code execution (CVSS 9.6 · EPSS 0%)

The fix

Upgrade Chrome: 156.0.8078.47 · 155.0.8059.39 · 155.0.8059.79 or later on your release line

Who is exposed: Chrome before 155.0.8059.39

Where it stands

  • No known exploitation

How it unfolded

  1. 16 Oct, Microsoft Security Response Center (official): Chromium CVE-2026-106329: Incorrect authorization
  2. 16 Oct, Microsoft Security Response Center (official): Chromium CVE-2026-106417: Integer overflow
  3. 16 Oct, Microsoft Security Response Center (official): Chromium CVE-2026-110136: Use after free

Connects to

Why it is Yellow

  • CVSS 6.5 medium

References

Original description

Memory corruption in Loader in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Low)

Last activity 20 Oct 2026. Patch Forecast updates every hour.