CVE-2026-106279: Incorrect reference resolution in Passwords

Published May 16, 2026
·
Updated

Chromium CVE-2026-106279: Incorrect reference resolution

Other sources

Incorrect reference resolution in Passwords in Google Chrome on on iOS prior to 155.0.8059.39 allowed a local attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a local program. (Chromium security severity: Medium)

— 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

4 affected componentsFixes available
Google Chrome<155.0.8059.39
155.0.8059.39
All of the following
Google Chrome<155.0.8059.39
Apple iPhone OS
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 Google Chrome for iOS to a version that resolves this vulnerability.

    Fixed in 155.0.8059.39

Event History

May 16, 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 realistically exposed to this issue?

The issue affects Google Chrome on iOS before version 155.0.8059.39. Exploitation requires a local attacker that has already compromised the renderer process, so it is not described as a standalone remote attack.

2

What does an attacker need to exploit it?

An attacker needs local access and must have compromised Chrome's renderer process. The vulnerability may then allow arbitrary code execution outside Chrome's sandbox through a local program.

3

How can I determine whether an installation is affected?

Check the installed Google Chrome version on iOS. Versions earlier than 155.0.8059.39 are affected according to the provided information.

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