CVE-2026-95370 in Chromeinfo

Summary

by MITRE • 09/29/2026

Inappropriate implementation in NFC in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to bypass system access restrictions via a crafted HTML page. (Chromium security severity: Medium)

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 09/29/2026

The vulnerability identified as an inappropriate implementation within the Near Field Communication subsystem of Google Chrome, specifically in versions prior to 154.0.8037.57, represents a significant breach in browser-level access control mechanisms. This flaw allows for the bypassing of system access restrictions through the exploitation of how the browser handles NFC-related APIs and permissions when invoked from web content. The core technical issue lies in the improper validation or enforcement of security boundaries between untrusted web pages and sensitive device hardware interfaces. When a malicious actor crafts an HTML page designed to interact with NFC capabilities, the browser fails to correctly restrict access based on user consent or origin-based policies, effectively allowing remote code execution contexts to gain unauthorized privileges over local system resources that should remain isolated from web-originated scripts.

From a technical perspective, this vulnerability falls under the category of improper privilege management and insufficient verification of administrative privileges within client-side applications. The attack vector is classified as remote because it requires no prior access or authentication on the target machine; instead, it relies solely on social engineering tactics to lure a user into visiting a malicious website hosted by an attacker. Once the crafted HTML page is loaded, it leverages the NFC interface implementation flaws to execute actions that exceed its intended permissions. This could involve reading sensitive data stored on nearby NFC tags or writing unauthorized information to them without proper authorization checks being enforced by the browser's security sandbox. The severity of this vulnerability is rated as medium because while it does not directly lead to full system compromise, it enables a significant escalation in capabilities for an attacker who can successfully deliver the exploit payload.

The operational impact of this flaw extends beyond simple data leakage or modification. By bypassing access restrictions, an attacker could potentially exfiltrate confidential information stored on NFC-enabled devices such as smart cards, transit passes, or identification badges that users may have tapped near their device while browsing malicious content. Furthermore, the ability to write to these tags without restriction poses a risk of physical security breaches if those tags control access to secure areas or systems. This vulnerability undermines the trust model of web browsers by allowing untrusted code to interact with hardware interfaces in ways that were not intended by the platform designers. It highlights a critical gap in how modern browsers mediate between high-level application logic and low-level device drivers, particularly for emerging technologies like NFC which require careful handling due to their proximity-based nature and potential use in authentication scenarios.

To mitigate this risk, users must immediately update Google Chrome to version 154.0.8037.57 or later where these access control checks have been hardened. Administrators should enforce automatic updates across all endpoints within an organization to ensure consistent protection against such browser-based exploits. Additionally, security awareness training is recommended to educate employees about the risks of visiting untrusted websites and interacting with NFC tags from unknown sources while using web browsers that may not yet be patched. From a defensive engineering standpoint, this incident reinforces the need for rigorous code reviews focusing on permission models in hardware access APIs and regular penetration testing targeting browser-based attack vectors involving peripheral devices. The vulnerability aligns with CWE-269 Improper Privilege Management and can be mapped to MITRE ATT&CK techniques related to initial access via spearphishing links leading to exploitation of client-side software vulnerabilities, emphasizing the importance of keeping all components of the user's environment up to date to prevent such bypasses.

Responsible

Chrome

Reservation

09/22/2026

Disclosure

09/29/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you need the next level of professionalism?

Upgrade your account now!