CVE-2026-106252: Incorrect comparison in Fonts

Published May 15, 2026
·
Updated

Chromium CVE-2026-106252: Incorrect comparison

Other sources

Incorrect comparison in Fonts in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Low)

— NVD

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

Credit

Google

Affected Software

3 affected componentsFixes available
Google Chrome<155.0.8059.39
155.0.8059.39
Google Chrome<155.0.8059.39
Microsoft Edge (Chromium-based)<155.0.4283.45
155.0.4283.45

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.8059.39
  2. Upgrade

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

    Fixed in 155.0.4283.45
  3. Upgrade

    Upgrade Chromium to a version that resolves this vulnerability.

    Fixed in 155.0.8059.39

Event History

May 15, 2026
CVE Published
12:00 AM
Data Sourced
12:00 AM
SeverityWeaknessAffected Software
Oct 6, 2026
CVE Published
via MITRE·06:41 PM
Data Sourced
via MITRE·06:41 PM
DescriptionWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeaknessAffected Software
Oct 16, 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

Who is exposed to this issue?

Users of Google Chrome versions earlier than 155.0.8059.39 are affected when they visit a crafted HTML page.

2

What does an attacker need to exploit it?

The CVSS vector indicates network access, low attack complexity, no attacker privileges, and user interaction. The attacker would need to induce the user to load a crafted HTML page.

3

Does successful exploitation escape Chrome's sandbox?

No. The available description states that arbitrary code execution is possible inside the sandbox; it does not indicate a sandbox escape.

4

How can I determine whether Chrome is affected?

Check the installed Chrome version. Versions prior to 155.0.8059.39 are affected according to the provided advisory.

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