Loading story…
Chromium fixed CVE-2026-95355, a privilege-escalation flaw in iOS Chromium's CRWWKNavigationHandler. An attacker that had already achieved renderer code execution could forge navigation to the bundled error_page_loaded.html file, making the browser treat attacker-controlled content as a trusted local error page.
The trusted error-page state could then allow navigation to a privileged chrome:// WebUI URL and expose native WebUI bindings to the compromised renderer, enabling a sandbox escape. Chromium addressed the issue on August 21, 2026, in commit bb617c8b09d43ed4d617d0c2b6769899324c9ee8 by validating error-page navigations against browser-side state and restricting navigations from committed error pages; the fix was targeted for M154 release notes.
See affected versions and whether adversaries are exploiting it.
5 events from the most recent confirmed update back to the earliest known activity.
The iOS Chromium privilege-escalation issue was registered as CVE-2026-95355. Chromium also updated its vulnerability release-notes target to 0-M154.
Chromium committed bb617c8b09d43ed4d617d0c2b6769899324c9ee8, “ios: Validate error page navigations in CRWWKNavigationHandler,” and marked the issue fixed. The change restricts local error-page navigation to browser-initiated, safe history/reload, or securely managed session-restoration cases.
A proposed fix based on pending NavigationContext state was not accepted after testing showed it still allowed a webpage to load an error page directly.
Initial reproduction from ordinary webpage JavaScript failed because WebKit blocked local file loads. Chromium developers later confirmed that a compromised renderer could bypass the renderer-side local-resource checks and reach the vulnerable native navigation handling.
An experimental security project identified a potential confused-deputy flaw in Chromium for iOS error-page navigation handling. The flaw could let an already compromised renderer forge a bundled error-page navigation and ultimately obtain privileged WebUI bindings.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Google fixed **CVE-2026-95301**, a high-severity Chromium Site Isolation bypass in the extensions accessibility-automation infrastructure. A compromised, site-locked web renderer could bind the previously unprotected `RendererAutomationRegistry` interface and register a rogue automation receiver without browser-side authorization. If a legitimate `chrome.automation` consumer was active, the rogue receiver could obtain serialized accessibility-tree data from other origins and tabs, including visible page text, non-password form values, ARIA content, and cross-site frame URLs; the flaw also had potential cross-profile and Incognito exposure. Chromium now verifies that the calling renderer hosts an enabled extension with automation permission and terminates unauthorized renderers; the fix was targeted for Chrome M154 release notes.
Sep 23, 2026
Google Chrome addressed three **use-after-free** vulnerabilities tracked as `CVE-2026-7347`, `CVE-2026-7363`, and `CVE-2026-7344` in versions prior to `147.0.7727.138`. The bugs affect the **Chromoting**, **Canvas**, and **Accessibility** components, respectively, and all were classified under `CWE-416`. Two of the flaws were rated **critical**: `CVE-2026-7363` allows a remote attacker to execute arbitrary code inside the browser sandbox on Linux and ChromeOS by luring a user to a crafted HTML page, while `CVE-2026-7344` could let an attacker escape Chrome's sandbox on Windows after compromising the renderer process via crafted web content. The third issue, `CVE-2026-7347`, was rated **high severity** and affects Chromoting, where malicious network traffic could enable arbitrary code execution without privileges or user interaction. CVSS data added to the records shows network-based exploitation with high impact to confidentiality, integrity, and availability, with `CVE-2026-7363` and `CVE-2026-7344` carrying the vector `AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`. The vulnerabilities were documented in Chrome and Chromium tracking references, underscoring the need for organizations to move affected browsers to `147.0.7727.138` or later.
Jun 29, 2026
Google Chrome patched two high-severity vulnerabilities affecting desktop builds on **Windows, Linux, and macOS** before version `146.0.7680.178`. The first, `CVE-2026-5282`, is an out-of-bounds read in **WebCodecs** that could be triggered if a user opens a crafted HTML page, potentially exposing sensitive memory and causing a crash. NVD classified the flaw as `CWE-125` and scored it with the vector `AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H`, indicating remote exploitation with low complexity but requiring user interaction. The second flaw, `CVE-2026-5289`, is a **use-after-free** in Chrome's **Navigation** component that could allow an attacker who has already compromised the renderer process to potentially escape the browser sandbox through a crafted HTML page. NVD mapped the issue to `CWE-416` and assigned the vector `AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`, reflecting the risk of broader compromise across confidentiality, integrity, and availability. Google referenced both issues in its Chrome stable channel advisory and linked them to Chromium issue tracker entries, making version `146.0.7680.178` the key remediation point for affected users and enterprises.
Jun 29, 2026