Loading vulnerability…
CVE-2026-2313 is a high-severity use-after-free vulnerability in the CSS component of Google Chrome before version 145.0.7632.45. Crafted HTML content can trigger use of memory after it has been freed, resulting in heap corruption. The issue is remotely reachable through browser-rendered web content and is rated High by Chromium.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
20 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability referenced in Gentoo GLSA-202608-31; technical details are not provided in the content.
Unauthenticated SQL injection in the Ally (Elementor) WordPress plugin via improper sanitization/escaping of a user-supplied URL parameter in `get_global_remediations()`, enabling time-based blind SQLi to extract sensitive database information under certain configuration conditions.
A high-severity use-after-free vulnerability in Chrome’s CSS component that could allow remote code execution.
A high-severity use-after-free vulnerability in Google Chrome's CSS component that could allow arbitrary code execution.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.