CVE-2026-106342 in Chromeinfo

Summary

by MITRE • 10/07/2026

Information leak in Autofill in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to obtain sensitive information via a crafted HTML page. (Chromium security severity: Medium)

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 10/08/2026

The vulnerability identified as an information leak within the autofill functionality of Google Chrome versions preceding 155.0.8059.39 represents a significant privacy and security concern for end-users. This flaw allows a remote attacker to extract sensitive data that is typically masked or protected by browser security mechanisms. The attack vector involves the creation of a specially crafted HTML page, which exploits weaknesses in how Chrome handles autofill data during form interactions. By leveraging this vulnerability, an adversary can bypass standard privacy controls and access personal information such as names, addresses, credit card numbers, or other credentials stored within the user's browser profile. This type of incident falls under the category of unauthorized information disclosure, where confidential data is exposed to entities that should not have access to it, thereby compromising the integrity and confidentiality guarantees provided by the web application environment.

From a technical perspective, this vulnerability likely stems from improper handling or sanitization of autofill fields during specific user interactions or page loads. When a malicious webpage triggers autofill operations, the browser may inadvertently expose underlying data structures or values that are intended to be hidden for security purposes. This could occur due to race conditions, insufficient validation of input contexts, or flaws in the JavaScript execution environment related to form submission and field population. The severity is classified as medium by Chromium because while it does not allow direct code execution on the victim's machine, it facilitates a serious breach of user privacy. Attackers can use this capability for identity theft, financial fraud, or further social engineering attacks by gaining insight into the target's personal habits and stored credentials.

The operational impact of this vulnerability is substantial, particularly in environments where users store sensitive information directly in their browsers without additional encryption layers. If an attacker successfully exploits this flaw through a crafted HTML page hosted on a malicious website or embedded via cross-site scripting vectors, they can harvest autofill data remotely. This compromises the user's digital identity and may lead to unauthorized transactions if financial details are exposed. Furthermore, the availability of such detailed personal information increases the risk of targeted phishing campaigns, where attackers use known personal details to craft highly convincing fraudulent communications. The ease of exploitation via a simple HTML page means that users visiting compromised or maliciously designed websites are at immediate risk without any additional interaction required beyond loading the page in an affected browser version.

To mitigate this vulnerability, it is imperative for all users and organizations employing Google Chrome to update immediately to version 155.0.8059.39 or later, where these issues have been addressed by the Chromium team. Security administrators should enforce automatic updates within their enterprise environments to ensure that endpoints are protected against known exploits in web browsers. Additionally, users can reduce risk by disabling autofill for sensitive fields such as credit card numbers and passwords through browser settings, opting instead for dedicated password managers with stronger encryption models. Regular security awareness training is also recommended to help users recognize malicious websites and avoid interacting with untrusted content that might attempt to exploit browser vulnerabilities. Monitoring network traffic for unusual data exfiltration patterns can also aid in detecting potential exploitation attempts in real-time.

This incident aligns with Common Weakness Enumeration (CWE) categories such as CWE-200, which covers Exposure of Sensitive Information to an Unauthorized Actor, and potentially CWE-798 if it involves hardcoded or improperly secured credentials within the autofill mechanism. In terms of the MITRE ATT&CK framework, this vulnerability supports techniques related to Collection from Browser History (T1534) and Credential Access via Browser Extensions or Autofill features. Understanding these mappings helps security teams prioritize patching efforts and implement appropriate detection rules based on known adversary behaviors associated with browser-based data theft. Maintaining up-to-date software is the most effective defense against such web application vulnerabilities, as developers continuously refine security controls to close gaps that allow for unauthorized data access through standard web technologies.

Responsible

Chrome

Reservation

10/06/2026

Disclosure

10/07/2026

Moderation

accepted

EPSS

0.00244

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!