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

Exploitation

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

CVSS

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

EPSS

• CVE-2026-41327: 0.49% estimated exploitation activity in the next 30 days; percentile 42.19 (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.

1. Executive Summary A vulnerability has been found in Dgraph that gives an unauthenticated attacker full read access to every piece of data in the database. This affects Dgraph's default configuration where ACL is not enabled. The attack is a single HTTP POST to /mutate?commitNow=true containing a crafted cond field in an upsert mutation. The cond value is concatenated directly into a DQL query string via strings.Builder.WriteString after only a cosmetic strings.Replace transformation. No escaping, parameterization, or structural validation is applied. An attacker injects an additional DQL query block into the cond string, which the DQL parser accepts as a syntactically valid named query block. The injected query executes server-side and its results are returned in the HTTP response. There are no credentials involved. When ACL is disabled (the default), the /mutate endpoint requires no authentication. The authorizeQuery and authorizeMutation functions both return nil immediately…

Published by the source

11 Aug 2026, 20:19 UTC

Last modified by the source

11 Aug 2026, 20:45 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-mrxx-39g5-ph77

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GO-2026-5516

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

# Patch Next advisory brief: CVE-2026-41327

Advisory: Dgraph: Pre-Auth Full Database Exfiltration via DQL Injection in Upsert Condition Field
IDs: CVE-2026-41327, GHSA-mrxx-39g5-ph77
Record: https://patchnext.com/advisories/cve-2026-41327 (revision 2, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/dgraph-io/dgraph/v25 25.3.3; github.com/hypermodeinc/dgraph/v24 24.1.8. 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.3
- Go github.com/dgraph-io/dgraph: affected <= 1.2.8
- Go github.com/dgraph-io/dgraph/v24: affected <= 24.1.8
- Go github.com/hypermodeinc/dgraph/v24: affected < 24.1.8; fixed in 24.1.8

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/dgraph-io/dgraph/v25, github.com/dgraph-io/dgraph, github.com/dgraph-io/dgraph/v24, github.com/hypermodeinc/dgraph/v24.
- 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://osv.dev/vulnerability/GO-2026-5516 (OSV record GO-2026-5516 lists affected ranges: Go github.com/dgraph-io/dgraph >=0; Go github.com/dgraph-io/dgraph/v25 >=0 =0 <24.1.8 (fixed))
- Verified: https://github.com/advisories/GHSA-mrxx-39g5-ph77 (GitHub-reviewed advisory GHSA-mrxx-39g5-ph77 lists affected ranges: Go github.com/dgraph-io/dgraph/v25 >=0 =0 =0 <=1.2.8)

Commands are suggestions: review each one before running it.