# CVE-2026-109823: Host filesystem path disclosure via DNS rebinding


- **Severity:** Low 2.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** EEF-CVE-2026-109823, GHSA-cw46-9gf7-56p5

## What is CVE-2026-109823?

CVE-2026-109823 is a low-severity vulnerability in tidewave-ai tidewave, published on 27 Oct 2026. 

### Official 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.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

## Which versions are affected by CVE-2026-109823?

1 open source package ship an affected version, including tidewave.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tidewave` | Hex | From 0.8.0 | 0.9.2 |

## How do I fix CVE-2026-109823?

Upgrade tidewave to 0.9.2 or later.

## Is CVE-2026-109823 being exploited?

There is no known exploitation of CVE-2026-109823 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109823 and fix it if it is affected.

What it is: CVE-2026-109823 is a low-severity vulnerability in tidewave-ai tidewave, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-109823 in the wild and no public exploit code.

Affected packages and fixed versions:
- tidewave (Hex): affected from 0.8.0; fixed in 0.9.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109823/ (Markdown: https://insights.sbomify.com/CVE-2026-109823/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109823
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109823
- OSV: https://osv.dev/vulnerability/CVE-2026-109823

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109823/
Summaries are generated and may contain mistakes; the official description above is the record.