Medium

Use-after-free in Ozone in Google Chrome

IdentifiersCVE-2026-11628CWE-416· Use After Free

CVE-2026-11628 is a critical use-after-free vulnerability in the Ozone component of Google Chrome. According to the provided content, affected versions are Chrome prior to 149.0.7827.103. The flaw arises from improper handling of object lifetime, leading to a stale pointer dereference after memory has been freed. Successful triggering can cause heap corruption and unexpected application crashes, and the available advisory context states that exploitation is possible by a local attacker with physical access to the device.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can corrupt heap memory in the browser process, causing crashes and potentially enabling further browser compromise. The supplied advisories characterize the issue as capable of leading to heap corruption and potentially broader compromise of the affected browser instance. Debian’s downstream advisory for Chromium notes that vulnerabilities addressed in this update set may result in arbitrary code execution, denial of service, or information disclosure, but the specific impact confirmed in the provided content for CVE-2026-11628 is heap corruption from a use-after-free condition.

Mitigation

If you can’t patch tonight, do this now.

No specific workaround is provided in the supplied content. Mitigation is to reduce local physical access to affected devices until patching can be completed and to update affected Chromium-based browsers promptly. Restarting the browser may be required for the update to take effect.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 149.0.7827.103 or later. For Chromium on Debian, upgrade to 149.0.7827.102-1~deb12u1 on oldstable (bookworm) or 149.0.7827.102-1~deb13u1 on stable (trixie). For Microsoft Edge (Chromium-based), upgrade to version 149.0.4022.62 or later, which incorporates the Chromium fix.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

2 SOURCESView more in app

security online infoNews

Jun 9, 2026

Chrome Security Update: Exploit in the Wild Fixed

A critical Chrome vulnerability mentioned as part of the update's security fixes; the content only states it could trigger unexpected application crashes.

chrome releases blogNews

Jun 8, 2026

Chrome Releases: Stable Channel Update for Desktop

A critical use-after-free vulnerability in Chrome's Ozone component.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity