CVE-2026-6313 is a high-severity security feature bypass in Google Chrome caused by insufficient policy enforcement in the browser's Cross-Origin Resource Sharing (CORS) handling. In affected Chrome versions prior to 147.0.7727.101 on Linux and prior to 147.0.7727.101/102 on Windows and Mac, a remote attacker who had already compromised the renderer process could use a crafted HTML page to leak cross-origin data that should have remained isolated by the browser's origin-based access controls. The flaw weakens enforcement of cross-origin restrictions within the renderer context and enables unauthorized access to data across origin boundaries.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.