Path Traversal in dbgate (CVE-2026-47669)
Summary
Path traversal in dbgate (CVE-2026-47669). Risk of unauthorized operations or information disclosure. Exploitable via POST /auth/login. Mitigation: upgrade to 7.1.9 or later.
Original description
The description as published by the source.
DbGate is cross-platform database manager. In versions 7.1.8 and prior, the unzipDirectory() function in packages/api/src/shell/unzipDirectory.js (line 27) does not validate that extracted file paths stay within the output directory. A malicious ZIP with ../ entries writes files anywhere on the filesystem. In the default Docker deployment, DbGate runs as root and the none auth provider issues JWT tokens without credentials via POST /auth/login, so this is exploitable by any network-adjacent attacker. Version 7.1.9 fixes the issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47669 has been found in dbgate.
Attackers can target a specific entry point like POST /auth/login over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade dbgate to 7.1.9 or later.
If unsure, ask your IT team or search "dbgate CVE-2026-47669" on the vendor's site.
CVE-2026-47669 (dbgate) — CWE-22
Attack surface: POST /auth/login / none
Patched: 7.1.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in dbgate. Attackers reach the vulnerable code path via POST /auth/login.
Check the vendor advisory for the affected versions of dbgate. Attack surface: POST /auth/login / none.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 7.1.9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /auth/login requests with malformed payloads or SQL meta-characters. Run grep -r 'dbgate' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'dbgate' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
dbgateを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /auth/login' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /auth/loginへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade dbgate to 7.1.9ステージング環境で 7.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /auth/login on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com