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

Cross-origin data leak in Google Chrome ServiceWorker policy enforcement

IdentifiersCVE-2026-9116CWE-693· Protection Mechanism Failure

CVE-2026-9116 is a high-severity insufficient policy enforcement vulnerability in the ServiceWorker component of Google Chrome. According to the provided content, Chrome versions prior to 148.0.7778.179 improperly enforced security policy constraints in ServiceWorker, allowing a remote attacker to trigger cross-origin data leakage via a crafted HTML page. The issue is described by Google/Chromium as affecting ServiceWorker policy enforcement rather than a memory corruption condition, indicating a browser security boundary failure in how cross-origin restrictions were applied or enforced within ServiceWorker-related processing.

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 can expose cross-origin data to a remote attacker, resulting in information disclosure and violation of the browser same-origin security model. The provided content does not state code execution or privilege escalation; the documented impact is leakage of data that should remain isolated across origins.

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 untrusted HTML content in affected Chrome/Chromium versions until updates are applied. Enterprise defenders can prioritize rapid browser update rollout and restart enforcement. No specific vendor-supplied workaround beyond patching is provided in the content.

Remediation

Patch, then assume compromise.

Update Google Chrome/Chromium to a fixed version. The provided content states the vulnerability affects Google Chrome prior to 148.0.7778.179, so remediation is to upgrade to Chrome 148.0.7778.179 or later on affected platforms, and to deploy the corresponding Chromium package updates from the vendor or distribution. Ensure browsers are restarted so the patched version is active.
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 activity

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