Lyrie
Critical CVE
CVSS 9.13 sources verified·1 min read
By Lyrie Threat Intelligence·4/24/2026

CRITICAL: CVE-2026-41327 (CVSS 9.1) — multiple products

CVE: CVE-2026-41327

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

Severity: CRITICAL

Status: Critical advisory

Affected

_See vendor advisory_

Summary

Dgraph is an open source distributed GraphQL database. Prior to 25.3.3, 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. This vulnerability is fixed in 25.3.3.

Verified Sources

References

  • https://github.com/dgraph-io/dgraph/releases/tag/v25.3.3
  • https://github.com/dgraph-io/dgraph/security/advisories/GHSA-mrxx-39g5-ph77
  • https://github.com/dgraph-io/dgraph/security/advisories/GHSA-mrxx-39g5-ph77

_Validated by the Lyrie Threat Intelligence Pipeline — 3 independent sources confirmed before publication. No speculation._

Lyrie Verdict

A vulnerability of this severity is exactly what Lyrie's anti-rogue-AI defense is built for: continuous, autonomous monitoring that doesn't wait for human reaction time.

Validated sources

  1. [1]NVD
  2. [2]GitHub Advisory
  3. [3]MITRE