CVE-2026-118318: Google Chrome vulnerability

Q: What does an attacker need to exploit this issue?

The attacker needs to cause a user to load a crafted HTML page. The issue can then allow remote memory reading in affected Chrome versions.

Q: Which Chrome versions are affected?

Google Chrome versions prior to 156.0.8078.73 are affected. Updating to 156.0.8078.73 or later addresses the affected version range.

Q: Are users exposed through normal web browsing?

Yes. Because exploitation is described as occurring through a crafted HTML page, users of affected Chrome versions may be exposed when visiting attacker-controlled or otherwise malicious web content.

Published Oct 27, 2026

Updated

Improper access control in V8 in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to read memory via a crafted HTML page. (Chromium security severity: High)

Affected Software

1 affected component

Google Chrome<156.0.8078.73

Event History

Oct 27, 2026

CVE Published

via MITRE·11:03 PM

Data Sourced

via MITRE·11:03 PM

DescriptionWeakness

Data Sourced

via NVD·11:17 PM

DescriptionWeakness

Frequently Asked Questions

What does an attacker need to exploit this issue?

The attacker needs to cause a user to load a crafted HTML page. The issue can then allow remote memory reading in affected Chrome versions.

Which Chrome versions are affected?

Google Chrome versions prior to 156.0.8078.73 are affected. Updating to 156.0.8078.73 or later addresses the affected version range.

Are users exposed through normal web browsing?

Yes. Because exploitation is described as occurring through a crafted HTML page, users of affected Chrome versions may be exposed when visiting attacker-controlled or otherwise malicious web content.

CVE-2026-118318: Google Chrome vulnerability

Affected Software

Event History

Frequently Asked Questions

What does an attacker need to exploit this issue?

Which Chrome versions are affected?

Are users exposed through normal web browsing?

Company

Resources

Contact

Frequently Asked Questions

What does an attacker need to exploit this issue?

Which Chrome versions are affected?

Are users exposed through normal web browsing?