Loading story…
Microsoft published security advisories for two Chromium vulnerabilities affecting its browser platform, including CVE-2025-2783, an incorrect handle issue in Mojo on Windows, and CVE-2025-13637, an inappropriate implementation flaw in Downloads. The advisories indicate the issues were tracked through Microsoft's Security Update Guide as Chromium-related weaknesses requiring browser security updates.
The flaws affect separate browser components and could expose Windows users to security risk if left unpatched, with one issue tied specifically to inter-process communication through Mojo and the other to download handling logic. Microsoft did not provide detailed public synopses in the notices, but the entries show the company issued coordinated guidance to ensure Chromium-based deployments receive the relevant fixes.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
Microsoft added CVE-2025-13637 to its Security Update Guide, describing a Chromium vulnerability related to inappropriate implementation in Downloads.
Microsoft added CVE-2025-2783 to its Security Update Guide, describing a Chromium vulnerability involving an incorrect handle in Mojo on Windows.
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.
msrc.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 added Security Update Guide entries for multiple third-party vulnerabilities, including **Chromium** flaws `CVE-2026-8574` and `CVE-2025-13223` and an **Adobe Systems Incorporated** issue tracked as `CVE-2024-20721`. The Chromium advisories identify a **use-after-free in Core** and a **type confusion in V8**, both bug classes commonly associated with browser instability and potential code-execution risk depending on exploit conditions. Microsoft also listed `CVE-2024-20721` as an **improper input validation** vulnerability that can cause **denial of service** in Adobe software. The entries appear in Microsoft's Security Update Guide as vendor-linked advisories, giving defenders a consolidated reference point to track affected third-party components and prioritize patch validation across browsers and Adobe-dependent environments.
Jul 12, 2026
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 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.
Jul 12, 2026