Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Use-after-free in Google Chrome Digital Credentials API

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

CVE-2026-4456 is a high-severity use-after-free vulnerability in the Digital Credentials API in Google Chrome prior to version 146.0.7680.153. According to the provided content, a remote attacker who had already compromised the renderer process could trigger the flaw via a crafted HTML page and potentially escape Chrome's sandbox. The issue is a memory-lifetime error in the Digital Credentials API where freed memory may be subsequently reused, creating the possibility of controlled memory corruption and unintended code execution in a more privileged browser context.

Share:
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.

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 could allow an attacker to turn a renderer compromise into a sandbox escape. In practical terms, this can enable execution outside the renderer sandbox boundary, increasing attacker control over the host, enabling access to resources normally restricted to the sandboxed renderer, and potentially facilitating further code execution, persistence, or follow-on compromise depending on the target environment.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting use of untrusted websites and web content, enforcing browser isolation where available, and minimizing the ability for renderer compromise to be chained with local privilege boundaries. Standard hardening measures such as rapid browser update deployment, restricting execution of untrusted content, and using additional endpoint controls may reduce risk, but no specific workaround is provided in the supplied content.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 146.0.7680.153 or later. The provided content indicates that Google fixed this issue in Chrome 146.0.7680.153/154 depending on platform, with 146.0.7680.153 specifically identified as the fixed version threshold for this vulnerability. Apply the corresponding Chromium-based browser updates from the vendor as they become available.
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.

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.
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 activity4

Community discussion across Reddit, Mastodon, and other social sources.