Google Web Designer CVE-2026-3223

Exploitation requires the victim to open or import a maliciously crafted archive (a ZIP-based Google Web Designer project, template, or asset bundle containing directory-traversal entry names) inside Google Web Designer 14.2.2.0 - this is the concrete Zip Slip precondition. The CVSS vector's UI:A (active user interaction) and AV:L (local) confirm this is NOT remotely triggerable and NOT automatable: an attacker cannot exploit it without first delivering the file to the target and getting a user to load it, which is the primary factor limiting real-world risk. No authentication or elevated privileges are needed within the application itself (PR:N), and the severity of impact may depend on the privilege level of the account running the application and the writability of sensitive target paths on the host.

Signals are internally consistent and point to a targeted, low-volume risk rather than mass exploitation. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:A) confirms a LOCAL vector requiring active user interaction - the victim must open a malicious archive - which fundamentally caps automatability and scale; this is not remotely wormable despite the 8.4 base score driven by VC:H/VI:H/VA:H. EPSS is negligible at 0.01% (1st percentile), and the CVE is NOT in CISA KEV, so there is no evidence of active exploitation. No public POC is referenced (the sole reference is a Google VRP report). The high score reflects severe impact IF a user is socially engineered into opening a poisoned file, but the local vector plus mandatory user interaction make this a moderate operational priority - real, but dependent on successful social engineering rather than opportunistic internet-facing attack.

An attacker crafts a malicious Google Web Designer project or template archive containing entries with '../' traversal paths and distributes it via email, a design-asset marketplace, or a shared drive. When a designer opens or imports the archive, the application writes attacker-controlled files outside the extraction directory - for example into a startup or configuration location - resulting in code execution or privilege escalation the next time that path is loaded. No public POC is currently identified, and the local attack vector means the attacker relies on convincing the victim to open the file.