The vulnerability allows an attacker to read filesystem path names used by Tidewave. The application exposes configuration via /tidewave/connect and a rendered toolbar, and does not validate the Host header. An attacker can perform a DNS rebinding attack, causing the client’s browser to send same‑origin requests to the loopback address, and capture the returned tag. The resulting path names can disclose the local username and the structure of the project, thereby leaking sensitive information about the deployment.

tidewave (tidewave‑ai) versions 0.8.0 up to 0.9.1 are affected. All later releases, including 0.9.2 and newer, contain the patch.

The CVSS score of 2.3 indicates a low severity risk. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. The attack requires a DNS rebinding setup and a victim to visit a maliciously crafted web page that redirects to the loopback address. Once the page loads, the browser will perform the same‑origin request to /tidewave/connect or the toolbar, enabling the attacker to read the filesystem path information. Because no Transport Layer Security is required beyond the same‑origin policy, the exploit is feasible on networks where DNS rebinding is possible and can be performed entirely in the victim’s browser.