CVE-2026-41327

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EPSS
34.3%
KEV
Not listed

Published

April 24, 2026

Last Modified

April 28, 2026

Advisory Details (2)

Auto-updated Apr 28, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Dgraph: Pre-Auth Full Database Exfiltration via DQL Injection in Upsert Condition Field · Advisory · dgraph-io/dgraph · GitHub

https://github.com/dgraph-io/dgraph/security/advisories/GHSA-mrxx-39g5-ph77
generic

Release v25.3.3 · dgraph-io/dgraph · GitHub

https://github.com/dgraph-io/dgraph/releases/tag/v25.3.3

Affected Packages

(3 across 1 ecosystem)
Go(3)
PackageVulnerable rangeFixed inDependents
github.com/dgraph-io/dgraph———
github.com/dgraph-io/dgraph/v24———
github.com/dgraph-io/dgraph/v25—25.3.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 136 total refreshes for this CVE.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-24 14:05 UTCEPSS rescore
  20. 2026-06-23 21:33 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
Show 75 more
  1. 2026-06-19 19:25 UTCEPSS rescore
  2. 2026-06-18 17:52 UTCEPSS rescore
  3. 2026-06-18 17:52 UTCEPSS rescore
  4. 2026-06-17 17:53 UTCEPSS rescore
  5. 2026-06-16 17:52 UTCEPSS rescore
  6. 2026-06-15 17:49 UTCEPSS rescore
  7. 2026-06-15 06:06 UTCEG score recompute
  8. 2026-06-15 01:51 UTCEG score recompute
  9. 2026-06-14 20:50 UTCEG score recompute
  10. 2026-06-14 16:37 UTCEG score recompute
  11. 2026-06-14 11:34 UTCEG score recompute
  12. 2026-06-13 23:00 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-06-12 12:17 UTCEG score recompute
  16. 2026-06-12 06:06 UTCEG score recompute
  17. 2026-06-12 01:55 UTCEG score recompute
  18. 2026-06-11 21:43 UTCEG score recompute
  19. 2026-06-11 17:32 UTCEG score recompute
  20. 2026-06-11 14:00 UTCEPSS rescore
  21. 2026-06-11 12:51 UTCEG score recompute
  22. 2026-06-10 22:18 UTCEPSS rescore
  23. 2026-06-10 20:59 UTCEG score recompute
  24. 2026-06-10 16:35 UTCEG score recompute
  25. 2026-06-10 13:22 UTCEPSS rescore
  26. 2026-06-10 13:22 UTCEPSS rescore
  27. 2026-06-10 12:24 UTCEG score recompute
  28. 2026-06-10 08:13 UTCEG score recompute
  29. 2026-06-10 04:01 UTCEG score recompute
  30. 2026-06-09 23:49 UTCEG score recompute
  31. 2026-06-09 18:07 UTCEG score recompute
  32. 2026-06-09 13:55 UTCEG score recompute
  33. 2026-06-09 09:43 UTCEG score recompute
  34. 2026-06-09 04:35 UTCEG score recompute
  35. 2026-06-09 00:23 UTCEG score recompute
  36. 2026-06-08 14:17 UTCEPSS rescore
  37. 2026-06-08 14:17 UTCEPSS rescore
  38. 2026-06-08 12:06 UTCEG score recompute
  39. 2026-06-08 07:46 UTCEG score recompute
  40. 2026-06-08 03:35 UTCEG score recompute
  41. 2026-06-07 23:23 UTCEG score recompute
  42. 2026-06-07 19:12 UTCEG score recompute
  43. 2026-06-07 15:25 UTCEPSS rescore
  44. 2026-06-07 15:25 UTCEPSS rescore
  45. 2026-06-07 15:01 UTCEG score recompute
  46. 2026-06-07 10:49 UTCEG score recompute
  47. 2026-06-07 06:38 UTCEG score recompute
  48. 2026-06-07 02:26 UTCEG score recompute
  49. 2026-06-06 22:02 UTCEG score recompute
  50. 2026-06-06 17:18 UTCEG score recompute
  51. 2026-06-06 13:47 UTCEPSS rescore
  52. 2026-06-06 13:47 UTCEPSS rescore
  53. 2026-06-06 12:35 UTCEG score recompute
  54. 2026-06-06 08:21 UTCEG score recompute
  55. 2026-06-06 04:10 UTCEG score recompute
  56. 2026-06-05 23:44 UTCEG score recompute
  57. 2026-06-05 22:47 UTCEPSS rescore
  58. 2026-06-05 19:18 UTCEG score recompute
  59. 2026-06-05 15:06 UTCEG score recompute
  60. 2026-06-05 10:54 UTCEG score recompute
  61. 2026-06-05 06:43 UTCEG score recompute
  62. 2026-06-05 06:10 UTCEPSS rescore
  63. 2026-06-05 06:10 UTCEPSS rescore
  64. 2026-06-05 02:31 UTCEG score recompute
  65. 2026-06-04 22:10 UTCEG score recompute
  66. 2026-06-04 17:57 UTCEG score recompute
  67. 2026-06-04 13:44 UTCEG score recompute
  68. 2026-06-04 13:12 UTCEPSS rescore
  69. 2026-06-04 13:12 UTCEPSS rescore
  70. 2026-06-04 09:32 UTCEG score recompute
  71. 2026-06-04 05:16 UTCEG score recompute
  72. 2026-06-04 01:04 UTCEG score recompute
  73. 2026-06-03 20:52 UTCEG score recompute
  74. 2026-06-03 16:39 UTCEG score recompute
  75. 2026-06-03 12:27 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41327?
CVE-2026-41327 is a critical vulnerability published on April 24, 2026. 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…
When was CVE-2026-41327 disclosed?
CVE-2026-41327 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on April 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41327 actively exploited?
CVE-2026-41327 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41327?
CVE-2026-41327 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-41327?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41327, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41327

Explore →

Is Your Infrastructure Affected by CVE-2026-41327?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs