Dgraph Vulnerable to DQL Injection via checkUserPassword GraphQL Query

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-44840: 0.53% estimated exploitation activity in the next 30 days; percentile 44.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The checkUserPassword GraphQL query in Dgraph is vulnerable to DQL (Dgraph Query Language) injection. User-supplied password values are interpolated directly into a DQL checkpwd() query via fmt.Sprintf without any escaping or parameterization. An attacker can inject a password containing a double-quote character to break out of the DQL string literal and append arbitrary DQL query blocks. Details Vulnerable Code Path The vulnerability exists in the GraphQL-to-DQL query rewriting layer: 1. queryrewriter.go (~line 364) — The checkpwd() DQL function is constructed using fmt.Sprintf: The raw password string from the GraphQL query input is embedded directly into the DQL query without escaping double quotes or other special characters. 2. graphquery.go — The constructed query attribute is serialized into the final DQL string via b.WriteString(query.Attr), passing the unsanitized content directly to the Dgraph query engine. Attack Mechanism A password value containing a double-quote…

Published by the source

29 Jun 2026, 22:53 UTC

Last modified by the source

29 Jun 2026, 22:53 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q2m9-6jp9-c6mc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44840

Advisory: Dgraph Vulnerable to DQL Injection via checkUserPassword GraphQL Query
IDs: CVE-2026-44840, GHSA-q2m9-6jp9-c6mc
Record: https://patchnext.com/advisories/cve-2026-44840 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/dgraph-io/dgraph/v25 25.3.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/dgraph-io/dgraph/v25: affected <= 25.3.3; fixed in 25.3.4

## Suggested inspection (read-only)
- Go github.com/dgraph-io/dgraph/v25: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/dgraph-io/dgraph/v25.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q2m9-6jp9-c6mc (GitHub-reviewed advisory GHSA-q2m9-6jp9-c6mc lists affected ranges: Go github.com/dgraph-io/dgraph/v25 >=0 <=25.3.3)

Commands are suggestions: review each one before running it.