Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-44840 – Unauthenticated DQL Injection Enabling Database Exfiltration in Dgraph (prior to…

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-44840 is a high-severity DQL (Dgraph Query Language) injection vulnerability in Dgraph, an open-source distributed GraphQL database, affecting all releases prior to version 25.3.4. The flaw allows unauthenticated remote attackers to inject arbitrary DQL query blocks through the checkUserPassword GraphQL query, enabling full exfiltration of database contents without any credentials. A patch is available in version 25.3.4.

Technical details

  • Root cause: The checkUserPassword GraphQL query builds a DQL checkpwd() query by interpolating user-supplied password values directly via fmt.Sprintf with no input escaping or parameterization, classified under CWE-943 (Improper Neutralization of Special Elements in Data Query Logic).
  • Trigger conditions: An attacker submits a crafted GraphQL checkUserPassword request containing a double-quote character within the password field; this character breaks out of the DQL string literal context, allowing arbitrary DQL content to be appended.
  • Attack vector: Exploitable remotely over HTTP on Dgraph’s GraphQL API endpoint (default port 8080), with no authentication, no prior privileges, and no user interaction required.
  • Impact: Successful exploitation enables the attacker to append arbitrary DQL query blocks that execute against the database and return results in the HTTP response, achieving full exfiltration of all stored data. Database integrity and availability are not affected.

Affected software

  • Dgraph all versions prior to 25.3.4

Severity

CVSS v3.1 Base Score: 7.5 (HIGH)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Dgraph to version 25.3.4 or later, which resolves the vulnerability by properly escaping or parameterizing user-supplied password values before they are interpolated into DQL queries.
  • If immediate patching is not feasible: Restrict network-level access to Dgraph’s HTTP GraphQL API (port 8080) to trusted IP ranges only, and remove any direct public internet exposure of the Dgraph endpoint until the upgrade can be applied.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge