Vulnerability in github.com/dgraph-io/dgraph/v25 (CVE-2026-44840)
Summary
Vulnerability in github.com/dgraph-io/dgraph/v25 (CVE-2026-44840). Confidential information can be exposed externally. Mitigation: upgrade to 25.3.4 or later.
Original description
The description as published by the source.
Dgraph is an open source distributed GraphQL database. Prior to version 25.3.4, 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. Version 25.3.4 patches the issue.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44840 has been found in github.com/dgraph-io/dgraph/v25.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade github.com/dgraph-io/dgraph/v25 to 25.3.4 or later.
If unsure, ask your IT team or search "github.com/dgraph-io/dgraph/v25 CVE-2026-44840" on the vendor's site.
CVE-2026-44840 (github.com/dgraph-io/dgraph/v25) — CWE-943 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 25.3.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-943) exists in github.com/dgraph-io/dgraph/v25.
Check the vendor advisory for the affected versions of github.com/dgraph-io/dgraph/v25.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 25.3.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/dgraph-io/dgraph/v25' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/dgraph-io/dgraph/v25' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/dgraph-io/dgraph/v25を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/dgraph-io/dgraph/v25 to 25.3.4ステージング環境で 25.3.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com