CVE-2026-106308
Google Chrome ≤ 155.0.8059.39
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-106308 is a high-severity Use of Incorrectly-Resolved Name or Reference (CWE-706) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).
Operationally, ranked at the 19th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-93803
Vulnerability Data
Incorrect reference resolution in Autofill in Google Chrome on on Android prior to 155.0.8059.39 allowed a remote attacker leveraging social engineering to obtain sensitive information via a crafted HTML page. (Chromium security severity: High)
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Network segmentation and routing policies reduce the chance that a mis-resolved name leads to an unintended external resource.
Segregated networks limit the blast radius when a name or reference resolves outside the intended control sphere.
Secure SDLC practices include design reviews that can catch incorrect name or reference handling before deployment.
A.8.26 only requires that security requirements (including those that could address name-resolution issues) be identified during development or acquisition; it does not itself enforce, implement, or stop exploitation of an incorrectly-resolved name or reference.
A.8.27 mandates security-by-design principles (least privilege, default-deny, distrust-external-input, security-oriented design reviews, hardening) that reach many but not all name-resolution mistakes; a bounded remainder (e.g. flawed resolution logic inside trusted components or libraries) can still be introduced and exploited.
Secure-coding standards directly address canonicalization, input validation and safe name resolution, mitigating CWE-706.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-706, a class-level weakness, and none of its children carries one either.