CVE-2026-109823

Host filesystem path disclosure via DNS rebinding

  • Low 2.3

Description

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.

Key facts

Published
27 Oct 2026
Last changed
4 Nov 2026
Assigned by
EEF
EPSS
0.368% likely to be exploited in the next 30 days, higher than 31.067% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 2.3CVSS 4.0, Lowfrom the CNA (EEF)CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

A malicious web page that a developer visits while the Phoenix development server runs can learn the developer's username, project location, and dependency layout on disk. This information helps an attacker prepare further attacks against the machine. (CNA impact statement)

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
tidewave-aitidewave
  • Default status: unaffected
  • 0.8.0 up to but excluding 0.9.2 (affected)
tidewave-aitidewave
  • Default status: unaffected
  • f78352b56d19cd4ae49999aa385011cef73e8b93 up to but excluding 80159536f752dc4d34797934d1516f29cea12b50 (affected)

Timeline

  1. 27 Oct 2026 Published

Weakness

References