CVE-2026-63637: Dgraph: DQL Injection via unvalidated regexp filter argument in GraphQL query rewriter
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-04 15:41 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Dgraph is an open source distributed GraphQL database. Prior to 25.3.8, maybeQuoteArg in graphql/resolve/query_rewriter.go passes regexp filter strings into generated DQL without quoting or validating the /pattern/flags form, allowing crafted GraphQL query or mutation filters to inject DQL operators, disclose unintended nodes, or expand modification and deletion targets. This issue is fixed in version 25.3.8.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-08-06).
Weakness: CWE-943: Improper Neutralization of Special Elements in Data Query Logic
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity low, availability low. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 5 references on Exploit Observer
Live scores
- EPSS
- 0.004
low predicted chance of attack - VEDAS
- 0.986
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| dgraph-io dgraph | version < 25.3.8 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-63637 Dgraph - GraphQL regexp Filter DQL Injection. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-63637 Dgraph - GraphQL regexp Filter DQL Injection"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/graphql"; nocase; http.request_body; content:"regexp"; nocase; fast_pattern; pcre:"/regexp[\x22'\s:]{1,8}[^\x22]{0,80}\x2f[a-z]{0,3}\s*\x29\s*(?:@|has\x28|uid\x28|eq\x28|type\x28|allof|anyof|\x7b)/i"; classtype:web-application-attack; reference:cve,CVE-2026-63637; reference:url,https://www.exploit.observer/?keyword=CVE-2026-63637&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=dgraph&match=exact; sid:1079405; rev:1;)
CVE-2026-63637.rules on GitHub
References
Other references
- https://github.com/dgraph-io/dgraph/security/advisories/GHSA-33p8-wc97-5qcj (x_refsource_CONFIRM)
- https://github.com/dgraph-io/dgraph/commit/aaff09ab9608f87d88e9d601e71d271306083392 (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
