Loading story…
Microsoft published Security Update Guide entries for multiple Chromium vulnerabilities affecting browser components including HID, ServiceWorker, V8, and the File Manager API. The newly listed issues include CVE-2026-8515, a use-after-free flaw in HID, and CVE-2026-9116, an insufficient policy enforcement bug in ServiceWorker, alongside earlier Chromium-tracked issues such as CVE-2024-4761 (out-of-bounds write in V8), CVE-2022-4262 (type confusion in V8), and CVE-2022-0107 (use-after-free in the File Manager API).
The advisories indicate continued Microsoft tracking of upstream Chromium security defects that can affect Chromium-based products, with the listed bugs spanning memory-corruption and policy-enforcement weaknesses commonly associated with browser compromise risk. The reference set also includes CVE-2019-1406, a separate Jet Database Engine remote code execution vulnerability, but the dominant event is Microsoft's publication of several Chromium-related vulnerability records covering browser engine and API attack surfaces.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
6 events from the most recent confirmed update back to the earliest known activity.
Microsoft published a Security Update Guide entry for CVE-2026-9116, a Chromium insufficient policy enforcement vulnerability in ServiceWorker.
Microsoft published a Security Update Guide entry for CVE-2026-8515, a Chromium use-after-free vulnerability in HID.
Microsoft published a Security Update Guide entry for CVE-2024-4761, a Chromium out-of-bounds write vulnerability in V8.
Microsoft published a Security Update Guide entry for CVE-2022-4262, a Chromium type confusion vulnerability in V8.
Microsoft published a Security Update Guide advisory for CVE-2022-0107, a Chromium use-after-free vulnerability in the File Manager API.
Microsoft published a Security Update Guide advisory for CVE-2019-1406, a remote code execution vulnerability in the Jet Database Engine.
6 references tracked. Mallory keeps watching after this page renders.
msrc.microsoft.com
Open sourcemsrc.microsoft.com
Open sourcemsrc.microsoft.com
Open sourceportal.msrc.microsoft.com
Open sourcemsrc.microsoft.com
Open sourceportal.msrc.microsoft.com
Open sourceMap 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.
Microsoft published security advisories for several **Chromium** vulnerabilities spanning browser components including **WebXR**, **WebRTC**, **V8**, and web apps. The issues are tracked as `CVE-2026-8583` (**insufficient policy enforcement in WebXR**), `CVE-2023-7024` (**heap buffer overflow in WebRTC**), `CVE-2022-1096` (**type confusion in V8**), and `CVE-2021-4052` (**use-after-free in web apps**), indicating exposure across both rendering and scripting-related functionality in Chromium-based environments. The listed flaws cover multiple high-risk bug classes commonly associated with browser compromise, including memory corruption and policy enforcement weaknesses. Microsoft surfaced the vulnerabilities through its Security Update Guide and portal advisories, signaling that organizations using Microsoft products that incorporate Chromium components should review applicable updates and assess browser-related attack surface tied to immersive web features, real-time communications, JavaScript execution, and web application handling.
Jul 3, 2026
Microsoft published Security Update Guide entries for a broad set of **Chromium** vulnerabilities affecting browser components including **WebRTC, ANGLE, Network, Navigation, Blink, Base, V8, Skia,** and **WebAudio**. The listed issues include multiple `use-after-free` bugs such as `CVE-2026-4445`, `CVE-2026-4454`, `CVE-2026-4449`, and `CVE-2026-4441`, as well as a `heap buffer overflow` in `ANGLE` (`CVE-2026-4448`), a `heap buffer overflow` in `WebAudio` (`CVE-2026-4443`), an `out-of-bounds read` in `Skia` (`CVE-2026-4460`), `insufficient validation of untrusted input` in `Navigation` (`CVE-2026-4451`), and an `inappropriate implementation` flaw in `V8` (`CVE-2026-4461`). The same set of advisories also included non-Chromium entries tied to lower-level platform components: `CVE-2026-4438` for `gethostbyaddr` and `gethostbyaddr_r` returning invalid DNS hostnames, `CVE-2025-71267` for an `ntfs3` infinite loop triggered by a zero-sized `ATTR_LIST`, and `CVE-2026-23233` for an `f2fs` fix to avoid mapping the wrong physical block for a swapfile. Together, the disclosures show Microsoft tracking both browser-engine memory-corruption risks and underlying filesystem and networking defects through its update pipeline.
Jun 29, 2026
Microsoft added **CVE-2026-9120** to its Security Update Guide as a **Chromium** flaw caused by a **use-after-free in WebRTC**, extending a pattern of browser-component memory-safety issues that have repeatedly affected Microsoft products built on Chromium. Related Microsoft advisories previously tracked similar upstream Chromium bugs including **CVE-2022-2294** (**heap buffer overflow in WebRTC**), **CVE-2022-2008** (**out-of-bounds memory access in WebGL**), **CVE-2021-4066** (**integer underflow in ANGLE**), and **CVE-2025-5419** (**out-of-bounds read/write in V8**). The broader set of Microsoft Security Update Guide entries also shows the company continuing to catalog third-party and legacy-component vulnerabilities that can lead to severe impact, including **OpenSSL CVE-2022-3602** affecting X.509 certificate verification and older **Jet Database Engine remote code execution** flaws such as **CVE-2019-0577**, **CVE-2019-0579**, and **CVE-2020-0995**. Together, the advisories highlight Microsoft's ongoing publication of high-risk memory-corruption and code-execution issues across browser, cryptographic, and database components that defenders should track for patching and exposure assessment.
Jul 3, 2026