CVE-2026-106182
Executive Summary
CVE-2026-106182 is a UI misrepresentation vulnerability in the Paint component of Google Chrome affecting versions prior to 155.0.8059.39. A remote attacker can exploit this flaw by crafting a malicious HTML page that spoofs UI elements, potentially misleading users into interacting with deceptive interface components. While the Chromium security severity is rated Medium and the CVSS score is 5.4, the vulnerability requires user interaction and can lead to limited confidentiality and availability impacts within a single security context.
This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.
No signup required
Technical Analysis
The vulnerability resides in Chrome's Paint subsystem, which is responsible for rendering visual elements of the browser's user interface. CWE-451 (User Interface (UI) Misrepresentation of Critical Information) describes a scenario where a user is presented with a UI that appears legitimate but is controlled or manipulated by an attacker to convey false information.
In this case, a remote attacker can craft an HTML page that causes Chrome's Paint component to misrender UI elements. This could manifest as spoofed dialogs, fake permission prompts, misleading address bar content, or deceptive overlay elements. The attack surface is the browser's rendering engine, specifically the Paint layer that composites and displays UI components.
The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L indicates:
- Attack Vector (Network): Exploitable remotely via the internet.
- Attack Complexity (Low): No special conditions are required beyond standard browsing.
- Privileges Required (None): The attacker does not need prior authentication.
- User Interaction (Required): The victim must visit a crafted HTML page.
- Scope (Unchanged): The impact remains within the browser's security context.
- Confidentiality (Low): Limited information disclosure may occur.
- Integrity (None): No direct data modification is possible.
- Availability (Low): Limited disruption to browser availability may occur.
The CNA title and NVD description provide insufficient technical detail regarding the exact rendering pipeline flaw, memory corruption, or logic error that enables the UI misrepresentation. No specific function names, API endpoints, or file paths are disclosed. The vulnerability class is a rendering integrity issue within the Paint component.
Exploitation Scenarios
Given the sparse technical detail, the attack chain is inferred from the vulnerability class and CVSS vector.
1) Reconnaissance / Target Identification: An attacker identifies targets running Google Chrome versions below 155.0.8059.39. This can be done through browser fingerprinting techniques, such as checking the User-Agent string or JavaScript feature detection. No public PoC exists, so the attacker must develop a custom exploit based on the known vulnerability class.
2) Triggering the Flaw: The attacker hosts a crafted HTML page on a server they control. When a victim visits this page, the HTML content triggers the UI misrepresentation condition in the Paint component. The exact trigger mechanism is not publicly documented, but it likely involves specific CSS, HTML elements, or rendering commands that cause the Paint layer to render deceptive UI elements. This could include fake browser chrome, spoofed security indicators, or misleading dialog boxes.
3) Payload / Execution Method: The payload is the crafted HTML page itself. No code execution, memory corruption, or privilege escalation is involved. The attack relies solely on visual deception. The attacker may use social engineering to lure victims to the page, such as phishing emails or malicious advertisements. Once loaded, the page misrepresents UI elements to trick the user into performing actions they believe are legitimate, such as entering credentials into a fake form or granting permissions to a malicious site.
4) Post-Exploitation Impact: The impact is limited to the misrepresentation itself. The attacker does not gain code execution or direct access to the victim's system. However, the spoofed UI could lead to credential theft, unauthorized actions, or further social engineering. The CVSS score reflects low confidentiality and availability impacts. No public PoC or exploit code is available; the attack chain is inferred from the vulnerability class.
Impact Assessment
The business impact of CVE-2026-106182 is moderate. Organizations relying on Google Chrome for web-based operations, particularly those in finance, healthcare, and government sectors where UI trust is critical, may face risks. The vulnerability requires user interaction, limiting its exploitability to social engineering campaigns. The blast radius is confined to individual browser sessions; no lateral movement or system compromise is possible based solely on this flaw.
The CVSS score of 5.4 reflects a Medium severity rating. The confidentiality impact is low, as an attacker might glean limited information through deceptive prompts. The integrity impact is none, as no data modification occurs. The availability impact is low, potentially causing browser instability or crashes in rare cases. The scope remains unchanged, meaning the vulnerability does not allow escaping the browser's sandbox or affecting other system components.
Affected systems include any environment running Google Chrome versions below 155.0.8059.39. Given Chrome's widespread adoption, the potential attack surface is vast, but the requirement for user interaction and the lack of public exploits reduce the immediate threat level. No CISA KEV listing indicates no known active exploitation in the wild.
Detection Guidance
Sigma Rule
title: Chrome UI Misrepresentation Exploitation Attempt
id: 7a8b9c0d-1e2f-3a4b-5c6d-7e8f9a0b1c2d
status: experimental
description: Detects potential exploitation of CVE-2026-106182 via crafted HTML pages
author: Threat Intelligence Team
date: 2026-05-20
logsource:
category: proxy
product: webserver
detection:
selection:
cs-method: 'GET'
cs-uri-query|contains:
- 'chrome'
- 'paint'
- 'ui-spoof'
sc-status: 200
condition: selection
falsepositives:
- Legitimate web traffic containing these strings
level: medium
tags:
- attack.t1189
- cve.2026.106182
YARA Rule
rule CVE_2026_106182_Chrome_UISpoof
{
meta:
description = "Detects HTML pages attempting Chrome UI misrepresentation (CVE-2026-106182)"
author = "Threat Intelligence Team"
date = "2026-05-20"
reference = "https://nvd.nist.gov/vuln/detail/CVE-2026-106182"
severity = "medium"
strings:
$s1 = "<iframe" nocase
$s2 = "chrome://" nocase
$s3 = "window.open" nocase
$s4 = "document.write" nocase
$s5 = "spoof" nocase
$s6 = "overlay" nocase
$s7 = "position:fixed" nocase
$s8 = "z-index" nocase
condition:
uint16(0) == 0x3C21 or uint16(0) == 0x6874
and 3 of ($s*)
}
Suricata IDS Rule
alert http $HOME_NET any -> $EXTERNAL_NET any (msg:"CVE-2026-106182 Chrome UI Misrepresentation Attempt"; flow:to_client,established; content:"Content-Type|3A| text/html"; http_header; content:"<iframe"; http_client_body; content:"chrome"; http_client_body; content:"overlay"; http_client_body; threshold:type limit, track by_src, count 1, seconds 60; classtype:attempted-user; reference:cve,2026-106182; sid:1000001; rev:1;)
Elastic Detection
sequence by process.entity_id
[process where process.name == "chrome.exe" and event.type == "start"]
[network where network.protocol == "http" and
url.path : "*" and
http.response.status_code == 200 and
process.name == "chrome.exe"]
Splunk SPL Query
index=web_logs sourcetype=access_combined
| search status=200 method=GET
| rex field=uri_path "(?<suspicious_path>.*)"
| search uri_query="*chrome*" OR uri_query="*overlay*" OR uri_query="*spoof*"
| stats count by src_ip, uri_path, uri_query, user_agent
| where count > 5
| sort - count
Wazuh OSSEC Rule
<group name="web,cve-2026-106182,">
<rule id="100200" level="7">
<if_sid>31100</if_sid>
<field name="url">chrome|overlay|spoof|paint</field>
<description>Possible CVE-2026-106182 Chrome UI misrepresentation attempt detected</description>
<mitre>
<id>T1189</id>
</mitre>
<group>cve_2026_106182,</group>
</rule>
</group>
Mitigation & Patch Guidance
Patch confidence: 0/4 — UNPATCHED. No patch evidence is available from any tracked source. The vulnerability is reported as fixed in Google Chrome 155.0.8059.39, but no official vendor advisory, patch commit, or CVE record with patch references has been observed.
1) Immediate Mitigations:
- Upgrade Google Chrome to version 155.0.8059.39 or later as soon as it becomes available in the stable channel.
- If upgrading is not immediately possible, enforce strict Content Security Policy (CSP) headers to limit the execution of untrusted scripts and iframes.
- Educate users about UI spoofing risks and encourage vigilance when interacting with unfamiliar web pages.
- Deploy browser extensions or enterprise policies that restrict the rendering of third-party content or disable JavaScript on untrusted sites.
- Monitor for unusual browser crashes or rendering anomalies that may indicate exploitation attempts.
2) Patch / Upgrade Steps:
- Verify the current Chrome version via
chrome://settings/help. - Enable automatic updates or manually download the latest version from the official Google Chrome website.
- For enterprise environments, use Google Update policies or Chrome Browser Cloud Management to push the update.
- Confirm the update by checking the version number after installation.
3) Long-Term Hardening:
- Implement a vulnerability management program that includes regular browser patching and version tracking.
- Use application allowlisting to prevent unauthorized browser versions from running.
- Deploy network-based detection for malicious HTML patterns and anomalous browser behavior.
- Conduct regular security awareness training focused on phishing and UI redressing attacks.
- Consider using a managed browser solution that enforces security policies and restricts user interaction with untrusted content.
References
- NVD — CVE-2026-106182: https://nvd.nist.gov/vuln/detail/CVE-2026-106182
- Google Chrome Release Notes (Version 155.0.8059.39): https://chromereleases.googleblog.com/
- CWE-451: User Interface (UI) Misrepresentation of Critical Information: https://cwe.mitre.org/data/definitions/451.html
- MITRE ATT&CK T1189 — Drive-by Compromise: https://attack.mitre.org/techniques/T1189/
- Chromium Security Severity Guidelines: https://www.chromium.org/developers/severity-guidelines
No known threat actor campaigns or exploit-in-the-wild evidence have been observed for this CVE. EPSS has not yet been scored by FIRST.org. No public PoC or exploit code is available.
What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.