n4ze3m · dialoqbase · CWE-22 · CWE-200 · CWE-287 · CWE-522 · published 2026-11-18
CVE-2026-63189Dialoqbase: Unauthenticated path traversal in GET /api/v1/view/* leads to arbitrary file read and full application takeover
Routine No exploitation evidence; EPSS 0.5%.
CVE-2026-63189 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 43% of all CVEs. This dialoqbase vulnerability: CVSS 9.8 (v3.1), attacks can be automated, a successful attack gives total control of the component. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.5% (43th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.8 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-22: Improper Limitation of a Pathname to a Restricted Directory · CWE-200: Exposure of Sensitive Information to an Unauthorized Actor · CWE-287: Improper Authentication · CWE-522: Insufficiently Protected Credentials
Affected versions (from the CVE record)#
- n4ze3m dialoqbase
< 1.11.5(affected)
Description (from the CVE record)#
Dialoqbase is an application for creating chatbots. Prior to 1.11.5, the unauthenticated GET /api/v1/view/* route in server/src/routes/api/v1/view/root.ts resolves its attacker-controlled wildcard path without normalization or containment, allowing traversal outside the intended uploads directory and arbitrary server file reads. Reading environment files can disclose DB_SECRET_KEY, the application’s JWT signing key, which permits forged administrator tokens and takeover of bots, conversations, integrations, and stored third-party credentials. This issue is fixed in version 1.11.5.
Quoted from the CVE Program record.