Unpatched Magento and Adobe Commerce Zero-Day Exploited to Backdoor Online Stores
CVE-2026-85046 affects the affected technology. Google on Thursday released security updates to patch 12 vulnerabilities, including one that has come under active exploitation in the wild.
What happened
Unpatched Magento and Adobe Commerce Zero-Day Exploited to Backdoor Online Stores. Attackers are exploiting a new unpatched vulnerability in Magento Open Source and Adobe Commerce that lets them run malicious code on an online store's server without logging in, Dutch e-commerce security company Sansec said in an advisory published on September 5. A security weakness in the affected technology is being tracked as CVE-2026-85046.
The high-severity vulnerability, tracked as CVE-2026-85046 (CVSS score: 8 8), has been described as a type confusion bug in V8, Chrome's JavaScript and WebAssembly engine. CVE-2026-85046 affects the affected technology. Google Releases Chrome Update to Patch Actively Exploited V8 Zero-Day.
Google has updated the Chrome browser to address an actively exploited high-severity zero-day flaw in the V8 engine and 11 other vulnerabilities. Google warns of new Chrome zero-day flaw exploited in attacks. Google on Thursday released security updates to patch 12 vulnerabilities, including one that has come under active exploitation in the wild.
Google Patches 6th Chrome Zero-Day of 2026. Sansec, which discovered the flaw and named it StyleSmuggler, said attacks started on September 4. Google’s Chrome 152 security update resolves 12 vulnerabilities, including a high-severity type confusion flaw in the V8 engine.
Editorial note: this News Brief follows the available evidence and adds length only when additional facts or useful context are available. Where public reporting does not establish a specific victim sequence, CyberDeltaForce does not present one as fact.
What the reporting and advisory establish
Attackers are exploiting a new unpatched vulnerability in Magento Open Source and Adobe Commerce that lets them run malicious code on an online store's server without logging in, Dutch e-commerce security company Sansec said in an advisory published on September 5.
Sansec, which discovered the flaw and named it StyleSmuggler, said attacks started on September 4.
"Sansec is publishing early
Unpatched Magento and Adobe Commerce Zero-Day Exploited to Backdoor Online Stores
Google on Thursday released security updates to patch 12 vulnerabilities, including one that has come under active exploitation in the wild. The high-severity vulnerability, tracked as CVE-2026-85046 (CVSS score: 8.8), has been described as a type confusion bug in V8, Chrome's JavaScript and WebAssembly engine. "Type confusion in V8 in Google Chrome prior to 152.0.7977.82 allowed a remote
Google Releases Chrome Update to Patch Actively Exploited V8 Zero-Day
Google warns of new Chrome zero-day flaw exploited in attacks
Google’s Chrome 152 security update resolves 12 vulnerabilities, including a high-severity type confusion flaw in the V8 engine.
What this means for your environment
Move from the published facts to the technical path, exposure conditions and defensive decisions that matter in a real environment.
Attack & Exploitation Path
The sequence below shows how the vulnerability can be reached and what successful exploitation can produce. Each stage is labeled by evidence status.
Required condition: Google Chrome is present and the vulnerable function is reachable in the way the software is normally used.
Required condition: attacker-controlled input or the relevant workflow reaches the affected code path.
Not publicly disclosed in enough technical detail to describe the mechanism without inference.
Not publicly disclosed in enough detail to state a specific post-exploitation result without inference.
Map Google Chrome to real assets, verify the vendor fix or mitigation, confirm the vulnerable path is no longer reachable, and review relevant telemetry for behavior consistent with exploitation.
Why this matters to you
CVE-2026-85046 matters because the practical risk is not the score alone — it is whether the affected technology or service exists in your environment and whether the reported trigger or exposure path can reach it. No exploitation flag is currently present in the CDF data, but that does not remove the need to validate affected systems.
Does this deserve attention in my environment?
Check the conditions below against your use of the affected technology or service.
Select the conditions that are true in your environment. Leaving a condition unselected does not mean you are safe — it only means you have not marked it as applicable.
- Search endpoint, software and asset inventory for the affected technology or service.
- Confirm the vendor-recommended fixed version or mitigation and verify deployment, not just assignment, across affected assets.
- Review relevant endpoint, application, network or identity telemetry for activity associated with exploitation of the affected component.
- Track vendor and government guidance for any change in exploitation status while remediation is underway.
What remains unconfirmed
- Available reporting does not currently indicate exploitation, but that can change as vendor, government or threat-intelligence reporting develops.
Sources & References
Original reporting and technical references are kept here for readers who want to verify the facts. Publisher names stay out of the reading flow above.