Cyber Resilience

CVE-2026-10022

HighUpdated

Published: 28 May 2026

Published
28 May 2026
Modified
17 June 2026
KEV Added
Patch
CVSS Score v3.1 7.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0015 4.7th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-10022 is a high-severity Type Confusion (CWE-843) vulnerability in Google Chrome. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 4.7th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability details

Type Confusion in V8 in Google Chrome prior to 148.0.7778.216 allowed an attacker who convinced a user to install a malicious extension to execute arbitrary code inside a sandbox via a crafted Chrome Extension. (Chromium security severity: Medium)

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1204.002 Malicious File Execution
An adversary may rely upon a user opening a malicious file in order to gain execution.
Why these techniques?

Type confusion in V8 enables client-side arbitrary code execution when triggered by a crafted malicious extension (T1203); requires user to install the extension (T1204.002).

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-5914Same product: Apple Macos
CVE-2026-7337Same product: Apple Macos
CVE-2026-10936Same product: Apple Macos
CVE-2026-10935Same product: Apple Macos
CVE-2025-8010Same product: Apple Macos
CVE-2026-5865Same product: Apple Macos
CVE-2025-13230Same product: Apple Macos
CVE-2026-4457Same product: Apple Macos
CVE-2026-10962Same product: Apple Macos
CVE-2026-11076Same product: Apple Macos

Affected Assets

google
chrome
≤ 148.0.7778.216 · ≤ 148.0.7778.215

Mitigating Controls

No mitigating controls mapped yet. The per-CVE control annotator has not reached this CVE.

References