You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
autofill vulnerability
About this tag
The autofill vulnerability tag on WindowsForum covers security flaws in browser autofill features, particularly in Chromium-based browsers like Google Chrome and Microsoft Edge on Windows. Discussions include CVE-2026-11636, a Windows-specific Chrome autofill use-after-free flaw fixed in version 149.0.7827.103, which poses memory-corruption risks and requires user interaction. Also covered is CVE-2024-11111, an inappropriate implementation in Chromium autofill affecting Microsoft Edge on Windows, disclosed by MSRC. These threads emphasize the importance of patching autofill vulnerabilities as part of endpoint risk management for Windows administrators, highlighting that such bugs, while not always headline-grabbing, can lead to serious security breaches.
Google Chrome before 149.0.7827.197 contains CVE-2026-13022, a high-severity Chromium Autofill flaw disclosed June 24, 2026, that can let a remote attacker who has already compromised the renderer process leak cross-origin data through a crafted HTML page. The bug is not a stand-alone “visit a...
Google Chrome CVE-2026-11636 was published by NVD on June 8, 2026, after Google disclosed a critical Windows-specific Autofill use-after-free flaw fixed in Chrome versions before 149.0.7827.103. The bug is not the loudest Chrome issue of the week, and that is precisely why it deserves attention...
Google Chrome’s CVE-2026-11291 is a low-severity Android Autofill flaw disclosed in June 2026 that affected Chrome for Android before version 149.0.7827.53 and could let a remote attacker bypass same-origin policy with a crafted HTML page. The bug is not the sort of headline-grabbing browser...
On November 14, 2024, the Microsoft Security Response Center (MSRC) issued a warning regarding a newly identified vulnerability within the Chromium framework, highlighted as CVE-2024-11111. This vulnerability, stemming from an inappropriate implementation in the Autofill feature of Chromium...