windows vulnerability

Google has patched a high-severity heap buffer overflow in PDFium that affects Chrome on Windows versions before 147.0.7727.101, closing off a path that could let an attacker execute code inside the browser sandbox through a crafted PDF. The fix landed in the April 15, 2026 Stable Channel...

Microsoft has published a new Windows vulnerability entry for CVE-2026-32091, describing it as a Microsoft Brokering File System Elevation of Privilege Vulnerability. The title alone signals a local privilege-escalation issue in a Windows component that historically sits close to the file system...

Microsoft has assigned CVE-2026-26143 to a PowerShell security feature bypass issue, and the way it is described suggests the company believes the vulnerability is credible enough to publish in the Security Update Guide rather than hold it back for later confirmation. That matters because...

Microsoft’s public vulnerability tracker lists CVE-2026-23668 as an Elevation of Privilege defect in the Windows Graphics Component, but the vendor has published only minimal public technical detail and no publicly verifiable proof‑of‑concept at the time of writing — making this a...

CISA has added a Microsoft Windows information‑disclosure vulnerability tracked as CVE‑2026‑20805 to its Known Exploited Vulnerabilities (KEV) Catalog, citing evidence of active exploitation and triggering urgent remediation expectations under Binding Operational Directive (BOD) 22‑01 for...

Microsoft’s security portal registers CVE-2026-20849 as a Kerberos-related elevation-of-privilege vulnerability in Windows, and the entry — while authoritative about impact class — leaves critical exploit mechanics and low-level root causes deliberately sparse; the vendor’s confidence signal...

Quick clarification before I write the long feature: I can't find any public record for CVE‑2026‑20818 at Microsoft’s Update Guide or other major trackers. The description you pasted matches a known Windows License Manager info‑disclosure (published Nov 11, 2025) — tracked as CVE‑2025‑62208 /...