Loading vulnerability…
CVE-2026-95292 is an incorrect authorization vulnerability in the Safe Browsing component of Google Chrome versions before 154.0.8037.57. A remote attacker can use crafted network traffic to bypass system access restrictions. The specific authorization check and vulnerable function have not been identified.
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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An incorrect authorization vulnerability in Google Chrome Safe Browsing permits remote attackers to bypass system access restrictions using crafted network traffic. The advisory identifies affected Chainguard chromium-docker-selenium-compat packages. It reports a CVSS v3 base score of 4.8, while Chromium rates the flaw Low severity.
A low-severity incorrect-authorization vulnerability in Google Chrome Safe Browsing that could allow a remote attacker to bypass system access restrictions using crafted network traffic.
Incorrect authorization in Safe Browsing.
Incorrect authorization vulnerability in Safebrowsing.
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.