cve.bz

CVE-2026-109823 tidewave-ai tidewave

2.3 lowEPSS 0.4%Fix available

Low (2.3) in tidewave-ai tidewave. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in tidewave 0.9.2.

On this page
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.

Severity

CVSS 4.0

2.3 low
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
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 31st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-497 Exposure of Sensitive System Information to an Unauthorized Control Sphere
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • tidewave (Hex): fixed in 0.9.2

Ask an AI about this CVE

Show the promptExplain CVE-2026-109823 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-109823?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-109823?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-109823 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
tidewave-ai tidewavefrom 0.8.0 before 0.9.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
EEF-CVE-2026-109823Hextidewave>=0.8.0 <0.9.20.9.2
EEF-CVE-2026-109823v0.9.0, v0.8.4, v0.8.1, v0.8.0no fix published

Attack patterns (CAPEC)

  • CAPEC-170 Web Application Fingerprinting Likelihood: High · Severity: Low
  • CAPEC-694 System Location Discovery Likelihood: High · Severity: Very Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON