CyberSecBulletin
CVE-2026-106279NVD status: Analyzed

Chrome: Use of Incorrectly-Resolved Name or Reference

Published Updated By the CyberSecBulletin desk

CVE-2026-106279 is a high-severity use of incorrectly-resolved name or reference vulnerability in Chrome from Google, with a CVSS 3.1 base score of 7.4 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. The record lists version 155.0.8059.39 as the first without the flaw, so updating Chrome to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.09% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Chrome to 155.0.8059.39 or a later version.
  2. Read the advisory on chromereleases.googleblog.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
GoogleChrome155.0.8059.39 up to, but not including, 155.0.8059.39155.0.8059.39

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).

Official description

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)

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use of Incorrectly-Resolved Name or Reference

The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.

More Use of Incorrectly-Resolved Name or Reference vulnerabilities (CWE-706)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other references

Other vulnerabilities in Chrome

All Chrome vulnerabilities

Recent Use of Incorrectly-Resolved Name or Reference vulnerabilities

Spotted an error? Tell us.