CVE-2026-109823: Host filesystem path disclosure via DNS rebinding
An attacker can read the name of filesystem paths of your application present via Tidewave configuration via /tidewave/connect or via the rendered toolbar.
Neither response checks the Host header. A web page that rebinds its own domain to the loopback address can therefore read the tag with a same-origin request, which carries no Origin header. The paths usually reveal the local username and the project layout.
This issue affects tidewave: from 0.8.0 before 0.9.2.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
tidewaveto a version that resolves this vulnerability.Fixed in 0.9.2
Event History
Frequently Asked Questions
Who is exposed to this issue?
Applications using Tidewave versions from 0.8.0 up to, but not including, 0.9.2 are affected. The disclosed information is limited to filesystem path names exposed through Tidewave configuration, which can reveal the local username and project layout.
What does an attacker need to exploit it?
An attacker needs a victim to load a web page under an attacker-controlled domain that can be rebound to the loopback address. The page can then make a same-origin request to /tidewave/connect or obtain the information from the rendered toolbar; these requests do not carry an Origin header.
Which endpoints expose the path information?
The path names can be read through /tidewave/connect or through the rendered Tidewave toolbar. Neither response validates the Host header in affected versions.
What version should be used to remediate the issue?
Upgrade Tidewave to version 0.9.2 or later. Versions before 0.8.0 are not identified as affected by the provided advisory.