Command Injection in dbgate-api (CVE-2026-47670)
Summary
Command injection in dbgate-api (CVE-2026-47670). Risk of unauthorized operations or information disclosure. Exploitable via functionName. Mitigation: upgrade to 7.1.9 or later.
Original description
The description as published by the source.
DbGate is cross-platform database manager. Versions 7.1.8 and prior are vulnerable to authenticated Remote Code Execution (RCE). Any user with valid DbGate credentials can execute arbitrary OS commands as root by exploiting an unsanitized functionName parameter in the /runners/load-reader endpoint. The require = null mitigation is trivially bypassed via dynamic import(). Version 7.1.9 contains a patch.
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-47670 has been found in dbgate-api.
Attackers can target a specific entry point like functionName over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade dbgate-api to 7.1.9 or later.
If unsure, ask your IT team or search "dbgate-api CVE-2026-47670" on the vendor's site.
CVE-2026-47670 (dbgate-api) — CWE-77
Attack surface: functionName / bundle.js
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.
A vulnerability (CWE-77) exists in dbgate-api. Attackers reach the vulnerable code path via functionName.
Check the vendor advisory for the affected versions of dbgate-api. Attack surface: functionName / bundle.js.
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 request patterns matching this CVE's known IOCs. Run grep -r 'dbgate-api' . 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-api' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
dbgate-apiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade dbgate-api to 7.1.9ステージング環境で 7.1.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com