Threat Feed

CVE-2026-63189: n4ze3m dialoqbase · Path traversal

Exploitation: None known · CVSS 9.8 Critical · Unauthenticated · Published 2026-11-18

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.

Enclave's analysis

Dialoqbase's GET /api/v1/view/* endpoint reads any server file an attacker names via a simple ../ path, with zero authentication required. The vendor advisory itself publishes the exact traversal payload, and reading the app's .env or /proc/self/environ leaks the JWT signing key — letting anyone forge an admin token and take over every bot, conversation and stored API key. No patch work needed beyond one GET request; fixed in 1.11.5, but the upstream repo is now archived, and operators must also rotate the secret key, not just upgrade.

Fix

Upgrade n4ze3m/dialoqbase to 1.11.5. No fixed version is listed for dialoqbase; follow the vendor advisory.

Affected versions

ProductVulnerableFixed in
dialoqbase< 1.11.5Not listed
n4ze3m/dialoqbase< 1.11.51.11.5

Seen in 2 sources