# CVE-2026-63637: Dgraph: DQL Injection via unvalidated regexp filter argument in GraphQL query rewriter

> Attackers can inject DQL operators via unvalidated regexp filters in GraphQL queries, leading to unauthorized data disclosure or modification in Dgraph databases.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-33p8-wc97-5qcj

## What is CVE-2026-63637?

CVE-2026-63637 is a high-severity code injection vulnerability in dgraph-io dgraph, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

## Which versions are affected by CVE-2026-63637?


## How do I fix CVE-2026-63637?

No fix has been published for CVE-2026-63637 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-63637 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63637 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63637 and fix it if it is affected.

What it is: CVE-2026-63637 is a high-severity code injection vulnerability in dgraph-io dgraph, published on 6 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63637 exists.

Affected product: dgraph-io dgraph. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63637/ (Markdown: https://insights.sbomify.com/CVE-2026-63637/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63637
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63637
- OSV: https://osv.dev/vulnerability/CVE-2026-63637

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63637/
Summaries are generated and may contain mistakes; the official description above is the record.