# CVE-2026-63637: Dgraph DQL injection via unvalidated regexp filter

Source: https://junglewise.ai/threats/cve-2026-63637-dgraph-dql-injection-via-unvalidated-regexp-filter  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-06. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-63637 · Severity: high · CVSS 8.6 · Published 2026-08-06

Dgraph is an open-source distributed GraphQL database used to store and query complex data. A vulnerability in its query rewriter allows attackers to inject arbitrary database commands through GraphQL queries and mutations that use regexp filters, enabling unauthorized data disclosure or bulk data modification without authentication. This could expose sensitive application data or allow attackers to delete or modify records en masse.

## Quick answers

**Is CVE-2026-63637 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-63637 being exploited in the wild.

**How severe is CVE-2026-63637?** High severity, with a CVSS score of 8.6, published 6 August 2026.

**Which products and versions are affected?** Dgraph Dgraph prior to 25.3.8.

**Is there a fix for CVE-2026-63637?** A patch was published on 2026-08-06: CVE-2026-63637 published; fix available in v25.3.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-63637 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-63637?** Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a DQL (Dgraph Query Language) injection in the maybeQuoteArg function in graphql/resolve/query_rewriter.go. The function explicitly skips sanitization for regexp filter arguments, passing user input directly into generated DQL without validation or escaping. An attacker sends a GraphQL query or mutation with a crafted regexp filter value that closes the regex literal, closes the function call, and injects arbitrary DQL operators (OR, has, eq, uid), which are then tokenized and executed as valid DQL syntax. Exploitation requires only network access and a schema with at least one @search(by: [regexp]) field; no authentication is required for queries, and mutations require only basic user-level auth. The attack bypasses intended query filters to retrieve all data or expands mutation/deletion targets. The fix validates regexp input format or uses DQL variable bindings, available in version 25.3.8.

## Affected products

- Dgraph Dgraph prior to 25.3.8

## Timeline

- 2026-07-17: disclosed: GitHub Security Advisory GHSA-33p8-wc97-5qcj published
- 2026-08-06: patched: CVE-2026-63637 published; fix available in v25.3.8

## References

- [https://github.com/dgraph-io/dgraph/commit/aaff09ab9608f87d88e9d601e71d271306083392](https://github.com/dgraph-io/dgraph/commit/aaff09ab9608f87d88e9d601e71d271306083392)
- [https://github.com/dgraph-io/dgraph/security/advisories/GHSA-33p8-wc97-5qcj](https://github.com/dgraph-io/dgraph/security/advisories/GHSA-33p8-wc97-5qcj)