ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-109823

Host filesystem path disclosure via DNS rebinding

Published Oct 27, 2026 · catalog updated Oct 27, 2026 · Host filesystem path disclosure

Last checked Nov 6, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-109823. EPSS is 0.37%. Act only if a listed version of Host filesystem path disclosure is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Host filesystem path disclosure).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Low2.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.37%
Remediation
Not established
Affected products
Hex tidewave · vendor tidewave-ai tidewave

## Summary 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 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 header. The paths usually reveal the local username and the project layout. This issue affects tidewave: from 0.8.0 before 0.9.2. ## Details **1. Data collection.** builds a map with ( ), ( ), , and . It HTML-escapes the JSON encoding of the map into . **2. Exposure.** serves the tag on . For all other routes, registers a callback that injects the tag into every response when . **3. Read access.** accepts any request without an header, and no code validates . After DNS rebinding, the browser sends a same-origin from a loopback peer. ## Proof of concept 1. Run a Phoenix or Plug application with on . 2. From a loopback peer, send with and , and no header. This is the request a DNS-rebound page makes. 3. The server answers . The meta tag contains the absolute project root and the dependency paths. 4. Send the same request to any HTML route of the application. The injected toolbar tag contains the same data. ## Impact 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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Hex tidewave0.8.0 → 0.9.2
  • vendor tidewave-ai tidewaveversion unspecified

How to fix CVE-2026-109823

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-109823. EPSS is 0.37%. Act only if a listed version of Host filesystem path disclosure is installed.

Which versions are affected?

Compare what you have installed with 0.8.0 → 0.9.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-497. EPSS 0.37%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 27, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    ## Summary 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 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 header. The paths usually reveal the local username and the pr

  2. Oct 27, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    tidewave fixed in 0.9.2

  3. Oct 27, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    tidewave fixed in 0.9.2

  4. Oct 27, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    ## Summary 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 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 header. The paths usually reveal the local username and the pr

Sources

  • CVE.orgVulnerability recordCVE-2026-109823

    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 t

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-109823

    30-day exploitation probability 0.37%

    first.org
  • OpenSSF OSV / OSV ScannerPackage advisoryEEF-CVE-2026-109823

    Host filesystem path disclosure via DNS rebinding

    osv.dev

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 6, 2026
  • OpenSSF OSV / OSV ScannerNov 2, 2026
  • CVE.orgOct 28, 2026