# CVE-2026-6215: DbGate REST/GraphQL openApiDriver.ts apiServerUrl1 server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in DbGate's REST/GraphQL component to access internal resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2026
- **Updated:** 14 Apr 2026
- **Also known as:** GHSA-gwqm-gx6r-h4cx

## What is CVE-2026-6215?

CVE-2026-6215 is a medium-severity server-side request forgery vulnerability in DbGate, published on 13 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A weakness has been identified in DbGate up to 7.1.4. The impacted element is the function apiServerUrl1 of the file packages/rest/src/openApiDriver.ts of the component REST/GraphQL. This manipulation causes server-side request forgery. The attack may be initiated 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-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-6215 being exploited?

There is no known exploitation of CVE-2026-6215 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6215 is a medium-severity server-side request forgery vulnerability in DbGate, published on 13 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6215 in the wild and no public exploit code.

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-6215/ (Markdown: https://insights.sbomify.com/CVE-2026-6215/index.md)
```

## Sources

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

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