Dyad Vulnerable to Remote Code Execution via Top-level Navigation in Preview Window

The vulnerability resides within Dyad's preview window functionality. An attacker can craft malicious web content that, when loaded within the preview, bypasses Docker container protections and executes arbitrary code on the host system. This effectively breaks the application's security boundaries, granting the attacker control over the underlying operating system. The potential impact is severe, including data theft, malware installation, and complete system takeover. The ability to bypass containerization significantly increases the attack surface and potential for widespread compromise, particularly in environments where Dyad is deployed within containerized infrastructure.

Developers and users of Dyad who are running versions 0.19.0 or earlier are at significant risk. This includes individuals using Dyad for local AI app development and organizations deploying Dyad within their development environments, particularly those utilizing containerization technologies where the bypass of container protections amplifies the potential impact.

• windows / supply-chain: Monitor PowerShell execution for suspicious commands related to Dyad's preview functionality. Check scheduled tasks for any unusual entries associated with Dyad.

Get-Process -Name Dyad | Select-Object -ExpandProperty Path

• linux / server: Examine system logs (journalctl) for errors or unusual activity related to Dyad's preview process. Use lsof to identify any unexpected files or network connections associated with Dyad.

lsof -p $(pidof Dyad)

• generic web: Monitor access logs for requests containing suspicious parameters or payloads targeting Dyad's preview endpoint. Inspect response headers for unexpected content or redirects.

1. 2025-09-17Disclosure

   disclosure

1. Reserviert2025-09-04
2. Veröffentlicht2025-09-17
3. EPSS aktualisiert2026-03-23

The primary mitigation is to immediately upgrade Dyad to version 0.20.0 or later, which contains the fix for this vulnerability. If upgrading is not immediately feasible, consider isolating Dyad instances from external networks to prevent potential exploitation. While a direct workaround is unavailable, implementing strict content security policies (CSP) within the Dyad application itself, if possible, could help mitigate the risk of malicious content execution. Monitor network traffic for unusual activity originating from Dyad instances, particularly requests to external domains or unexpected outbound connections.