dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-48017

HIGH · 8.8 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
DbGate is cross-platform database manager. In versions 7.1.8 and prior, the POST /runners/load-reader endpoint in DbGate accepts a functionName parameter that is directly interpolated into a JavaScript code template without any sanitization or validation. An authenticated user (with basic access, no special permissions required) can inject arbitrary JavaScript code that executes on the server with full process privileges, bypassing the require=null sandbox restriction. An authenticated user with basic access (no admin role, no run-shell-script permission required) can: execute arbitrary OS commands on the DbGate server with the privileges of the Node.js process, read/write any file accessible to the process, pivot to connected databases by reading connection credentials from DbGate's storage, and compromise the host system - in Docker deployments, this typically means root access within the container. Version 7.1.9 contains a patch.

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 · high confidence

DbGate versions 7.1.8 and prior contain an authenticated code injection vulnerability in the POST /runners/load-reader endpoint. The functionName parameter is directly interpolated into a JavaScript code template without sanitization, allowing any authenticated user (basic access level) to inject and execute arbitrary JavaScript code on the server with full Node.js process privileges, effectively achieving remote code execution and bypassing the require=null sandbox restriction.

MitigationUpgrade DbGate to version 7.1.9 or later. As an interim measure, restrict network access to the DbGate interface and review authentication controls until the patch can be applied.

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
High
Integrity
High
Availability
High

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

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 is running in your environment
    Identify processes listening on typical DbGate ports (default 3000) or check for dbgate process/service in your system inventory
    Affected if DbGate is actively running and accessible on the network
  2. Determine the installed DbGate version
    Check the package.json, Docker image tag, or application about page for the exact version number, then compare against the affected range (7.1.8 and prior)
    Affected if The installed version is 7.1.8 or any earlier version
  3. Verify the /runners/load-reader endpoint is accessible
    Check network exposure or firewall rules to confirm the /runners/load-reader path is reachable from your user workstations or the network
    Affected if The endpoint is reachable without additional network segmentation
  4. Confirm authentication is required for the endpoint
    Review access control settings or test the endpoint with an unauthenticated request to verify that authentication is enforced
    Affected if Any authenticated user (even with basic read-only access) can reach this endpoint
  5. Inspect recent access logs for the load-reader endpoint
    Review server access logs for POST requests to /runners/load-reader and examine the functionName parameter values for unexpected or suspicious patterns
    Affected if There are logged requests with unusual functionName values that suggest injection attempts

You are affected if DbGate version 7.1.8 or prior is running and the /runners/load-reader endpoint is accessible to authenticated users, since the functionName parameter can be exploited for arbitrary code execution.

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

Upgrade DbGate to version 7.1.9 or later. As an interim measure, restrict network access to the DbGate interface and review authentication controls until the patch can be applied.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-48017 — 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-48017 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