Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-mrxx-39g5-ph77

Dgraph: Pre-Auth Full Database Exfiltration via DQL Injection in Upsert Condition Field

CVSS 9.1 CriticalCriticalEPSS 0.0049 · 42nd percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 24 Apr 2026, 15:41 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/dgraph-io/dgraph/v25Go<25.3.325.3.3
github.com/dgraph-io/dgraph/v24Go<=24.1.8No fixed version yet
github.com/dgraph-io/dgraphGo<=1.2.8No fixed version yet
Identifiers
GHSA-mrxx-39g5-ph77 · CVE-2026-41327 · GO-2026-5516
Weakness (CWE)
CWE-943
Tags
Published
24 Apr 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Dgraph v25 before 25.3.3, v24 up to 24.1.8, and v1 up to 1.2.8 are affected. With ACL disabled (the default), an unauthenticated attacker who can reach the HTTP mutate endpoint can inject a query through the upsert condition field and read database contents. Upgrade v25 to 25.3.3; no fixed version is listed for v24 or v1.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.1 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0049, the 42nd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 24 Apr 2026, 19:17 UTC Confirmed by NVD
  2. 31 Oct 2026, 14:14 UTC First seen by agentprime
  3. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.