CVE-2026-109823

Tidewave DNS rebinding could reveal local project paths

tidewave-ai · tidewave

First documented disclosure · Review checkpoint

Summary

A visited page could read configured filesystem path names from a local developer service.

Severity and exploitation evidence

Low · 2.3/10 · CVSS 4.0. Severity source.

Exploitation not established: Malicious exploitation is not established by the reviewed originals. Public demonstrations and catalog absence do not establish exploitation status.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The connect response and rendered toolbar did not validate Host; a rebound same-origin request carries no Origin header.

Conditions required

A reachable affected local Tidewave service and a browser visiting attacker-controlled content that rebinds to loopback.

Potential impact

Configured paths can reveal the local username and project layout. Arbitrary file-content access is not established by this flaw.

Affected versions and configurations

tidewave: 0.8.0 through versions before 0.9.2.

Fix and mitigation status

0.9.2.

Practical next steps

Apply the issue-specific correction: 0.9.2.

Operating lesson

Validate request hosts on local development endpoints, including metadata routes.

Evidence and limits

Earliest reviewed public evidence 2026-10-26; CVE publication 2026-10-27. CVSS 4.0 2.3 is attributed to EEF in the CNA record.

Sources