# CVE-2026-101069: dbgate Export databaseConnections.js exportModelSql path traversal

> Remote attackers can exploit path traversal in dbgate's export function to read or modify arbitrary files on the system.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-8cww-26w7-j8m5

## What is CVE-2026-101069?

CVE-2026-101069 is a medium-severity path traversal vulnerability in dbgate, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in dbgate up to 7.3.1. Affected is the function exportModelSql of the file packages/api/src/controllers/databaseConnections.js of the component Export Handler. Executing a manipulation of the argument outputFile can lead to path traversal. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

No fix has been published for CVE-2026-101069 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-101069 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101069 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101069 and fix it if it is affected.

What it is: CVE-2026-101069 is a medium-severity path traversal vulnerability in dbgate, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101069 exists.

Affected product: dbgate. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101069/ (Markdown: https://insights.sbomify.com/CVE-2026-101069/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101069
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101069
- OSV: https://osv.dev/vulnerability/CVE-2026-101069

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101069/
Summaries are generated and may contain mistakes; the official description above is the record.