CVE-2026-101070: dbgate · Path Traversal
Affects dbgateSource CVE Database V5
Public exploit available · CVSS 6.9 Medium.
Data as of 13 Nov 2026, 23:53 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 28 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| dbgate | Affected
| Fixed in– |
npmdbgatepkg:npm/dbgateOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:dbgate:dbgate:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Since the vendor has not responded or provided a fix, users should monitor official channels for updates. Until a patch is available, consider restricting access to the affected endpoint or implementing additional input validation controls to mitigate exploitation risk.
Description
CVE-2026-101070 is a path traversal vulnerability in dbgate affecting versions 7.3.0 and 7.3.1. The flaw exists in the Files Endpoint component, specifically in the function handling the 'runid' argument in packages/api/src/controllers/runners.js. This vulnerability allows remote attackers to manipulate the 'runid' parameter to perform path traversal attacks. The vulnerability has a CVSS 4.0 score of 6.9 (medium severity). The vendor was contacted but did not respond, and no patch or fix information is currently available. Public exploit details have been disclosed, but no known exploits in the wild have been reported.