Loading story…
Microsoft published security advisories for two Chromium vulnerabilities affecting browser security components: CVE-2026-5872, a use-after-free in Blink, and CVE-2026-5899, an incorrect security UI issue in History Navigation. The flaws were listed in Microsoft's Security Update Guide as Chromium-related issues, indicating they affect browser code relied on by Microsoft products built on the Chromium engine.
The Blink memory-safety bug could expose users to instability or potential exploitation scenarios typical of use-after-free vulnerabilities, while the History Navigation flaw involves incorrect security indicators that could mislead users about page state or trust signals during navigation. Organizations using Microsoft browsers or platforms that incorporate Chromium components should review the relevant advisories and apply the associated security updates through normal patch management processes.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Microsoft added a Security Update Guide entry for CVE-2026-5882, a Chromium incorrect security UI vulnerability in Fullscreen. The reference provides no additional details about exploitation, impact, or remediation beyond the advisory listing.
Microsoft added a Security Update Guide entry for CVE-2026-5908, a Chromium integer overflow vulnerability in Media. The reference provides no additional details about exploitation, impact, or remediation beyond the advisory listing.
Microsoft added Security Update Guide entries for two Chromium vulnerabilities: CVE-2026-5872, a use-after-free issue in Blink, and CVE-2026-5899, an incorrect security UI issue in History Navigation. No additional incident, exploitation, or remediation details were provided in the references.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
14 references tracked. Mallory keeps watching after this page renders.
msrc.microsoft.com
Open sourcemsrc.microsoft.com
Open sourcemsrc.microsoft.com
Open sourcemsrc.microsoft.com
Open sourcemsrc.microsoft.com
Open sourcemsrc.microsoft.com
Open sourcemsrc.microsoft.com
Open sourcemsrc.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 a broad set of Chromium vulnerabilities affecting its browser platform, including `CVE-2026-7344` (use-after-free in Accessibility), `CVE-2026-7341` (use-after-free in WebRTC), `CVE-2026-7353` (heap buffer overflow in Skia), and `CVE-2026-7337` (type confusion in V8). Additional flaws patched include use-after-free bugs in Views, Media, GPU, Cast, and Navigation, along with insufficient validation of untrusted input in Compositing and an inappropriate implementation issue in Tint. The volume and variety of bugs indicate a significant browser security update focused on memory-safety and input-handling weaknesses in Chromium components commonly exposed through web content. Microsoft also listed `CVE-2026-31682`, a separate issue tied to `br_nd_send` and Neighbor Discovery option parsing, but the main body of advisories centers on Chromium-derived fixes that organizations should prioritize across Microsoft Edge deployments to reduce risk from malicious websites and crafted content.
Jul 12, 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 12, 2026