CVE-2026-110920: Memory corruption in V8 on 2026-10-04

Published Oct 15, 2026
·
Updated

Chromium CVE-2026-110920: Memory corruption in V8

Other sources

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

— MITRE

This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.

— Microsoft

Affected Software

3 affected componentsFixes available
Google Chrome<155.0.8059.84
Microsoft Edge<155.0.4283.62
155.0.4283.62
debian/chromium<=150.0.7871.100-1~deb12u1, <=150.0.7871.181-1~deb13u1
156.0.8078.73-1~deb12u1156.0.8078.73-1~deb13u1156.0.8078.47-1156.0.8078.79-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 155.0.4283.62
  2. Upgrade

    Upgrade debian/chromium to a version that resolves this vulnerability.

    Fixed in 156.0.8078.73-1~deb12u1Fixed in 156.0.8078.73-1~deb13u1Fixed in 156.0.8078.47-1Fixed in 156.0.8078.79-1
  3. Upgrade

    Upgrade Google Chrome (Chromium) to a version that resolves this vulnerability.

    Fixed in 155.0.8059.84

Event History

Oct 15, 2026
CVE Published
via MITRE·10:04 PM
Data Sourced
via MITRE·10:04 PM
DescriptionWeakness
Data Sourced
via NVD·10:19 PM
DescriptionSeverityWeaknessAffected Software
Oct 20, 2026
Data Sourced
12:00 AM
SeverityWeakness
Oct 26, 2026
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

Which Chrome versions are affected?

Google Chrome versions prior to 155.0.8059.84 are affected. Updating to 155.0.8059.84 or later addresses the issue.

2

What must an attacker do to exploit this vulnerability?

An attacker needs to cause a user to load a crafted HTML page remotely. Successful exploitation can execute arbitrary code inside the Chrome sandbox.

3

Is code execution outside the Chrome sandbox described?

No. The available information describes arbitrary code execution inside the sandbox only; it does not state that an attacker can escape the sandbox.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203