dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-6215

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Server-side request forgery (SSRF) vulnerability in DbGate's REST API component. The apiServerUrl1 function in packages/rest/src/openApiDriver.ts accepts user-controlled input to construct server URLs without proper validation, allowing attackers to make the server request arbitrary internal or external resources.

MitigationImplement strict allowlist-based URL validation for the apiServerUrl1 function to restrict requests to approved domains/IPs. Consider network segmentation and disabling direct external requests from the application server as compensating controls until a vendor patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm DbGate installation and version
    Check if DbGate is installed by looking for the application binary or node_modules containing 'dbgate' package. Run: npm list dbgate (if project-based) or check application files for dbgate version.json
    Affected if DbGate is installed and the version cannot be confirmed as patched (no patch version info available)
  2. Identify REST API component presence
    Locate the file packages/rest/src/openApiDriver.ts in the DbGate installation directory or source code repository. This file contains the vulnerable apiServerUrl1 function
    Affected if The openApiDriver.ts file exists with the apiServerUrl1 function present in the installation
  3. Check if REST API endpoint is accessible
    Attempt to access the REST API endpoint that uses apiServerUrl1. This is typically exposed on the configured DbGate server port (default often 5433 or similar). Send a test request to the API endpoint
    Affected if The REST API is exposed and accepts requests to endpoint paths that invoke the apiServerUrl1 function
  4. Verify lack of URL validation on apiServerUrl1
    Examine the source code of openApiDriver.ts for any URL validation, allowlisting, or sanitization logic before the apiServerUrl1 function uses user input to construct server URLs. Look for patterns like URL validators, allowlists, or regex checks
    Affected if No URL validation or allowlist-based restriction is found in the code before apiServerUrl1 processes user input for server URLs
  5. Test for SSRF vulnerability
    If you have access to test the API, send a request with a user-controlled parameter targeting apiServerUrl1 that includes an internal URL (e.g., http://localhost:port or http://127.0.0.1) to observe if the server makes the request
    Affected if The API accepts and processes arbitrary URLs provided by users without rejecting internal/private network addresses

A user is affected if DbGate is installed with the REST API component accessible and the apiServerUrl1 function in openApiDriver.ts lacks proper URL validation to prevent SSRF attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based URL validation for the apiServerUrl1 function to restrict requests to approved domains/IPs. Consider network segmentation and disabling direct external requests from the application server as compensating controls until a vendor patch is available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6215 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6215 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data