CVE-2026-34976 — AI Deep Analysis Summary

Q: What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Dgraph < 25.3.1 has a critical auth bypass in `restoreTenant`. 📉 **Consequences**: DB overwrite, SSRF, & server file read. Total compromise!

Q: Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: Missing authorization middleware on `restoreTenant` mutation. 🔓 **CWE**: CWE-862 (Missing Authorization).

Q: Who is affected? (Versions/Components)

📦 **Affected**: Dgraph versions **before 25.3.1**. 🏢 **Vendor**: dgraph-io. 📅 **Pub**: 2026-04-06.

Q: What can hackers do? (Privileges/Data)

💀 **Attacker Actions**: Unauthenticated access! 📂 Read server files. 🌐 Execute SSRF. 💾 Overwrite entire DB. 🚫 No login needed.

Q: Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: LOW. 🚫 **Auth**: None required (PR:N). 🎯 **Complexity**: Low (AC:L). 🖱️ **UI**: None needed (UI:N).

Q: Is there a public Exp? (PoC/Wild Exploitation)

🔍 **Public Exp**: No PoCs listed in data. 📰 **Ref**: GHSA-p5rh-vmhp-gvcw. ⚠️ **Risk**: High CVSS (Critical).

Q: How to self-check? (Features/Scanning)

🔎 **Check**: Scan for Dgraph < 25.3.1. 📡 **Feature**: Look for exposed `restoreTenant` endpoint. 🛠️ **Tool**: Version fingerprinting.

Q: Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: Yes! Upgrade to **Dgraph 25.3.1** or later. 📥 **Action**: Patch immediately via official release.

Q: What if no patch? (Workaround)

🚧 **No Patch?**: Block external access to `restoreTenant`. 🔒 **Mitigate**: Enforce strict API gateway auth. 🛑 **Isolate**: Network segmentation.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: CRITICAL. 🚨 **Priority**: P1. 🏃 **Action**: Patch NOW. CVSS is High/HIGH/HIGH. Zero-day risk!

Updated May 06, 2026 CVSS 10.0 · Critical

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Dgraph < 25.3.1 has a critical auth bypass in `restoreTenant`. 📉 **Consequences**: DB overwrite, SSRF, & server file read. Total compromise!

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: Missing authorization middleware on `restoreTenant` mutation. 🔓 **CWE**: CWE-862 (Missing Authorization).

Q3Who is affected? (Versions/Components)

📦 **Affected**: Dgraph versions **before 25.3.1**. 🏢 **Vendor**: dgraph-io. 📅 **Pub**: 2026-04-06.

Q4What can hackers do? (Privileges/Data)

💀 **Attacker Actions**: Unauthenticated access! 📂 Read server files. 🌐 Execute SSRF. 💾 Overwrite entire DB. 🚫 No login needed.

Q5Is exploitation threshold high? (Auth/Config)

⚡ **Threshold**: LOW. 🚫 **Auth**: None required (PR:N). 🎯 **Complexity**: Low (AC:L). 🖱️ **UI**: None needed (UI:N).

Q6Is there a public Exp? (PoC/Wild Exploitation)

🔍 **Public Exp**: No PoCs listed in data. 📰 **Ref**: GHSA-p5rh-vmhp-gvcw. ⚠️ **Risk**: High CVSS (Critical).

Q7How to self-check? (Features/Scanning)

🔎 **Check**: Scan for Dgraph < 25.3.1. 📡 **Feature**: Look for exposed `restoreTenant` endpoint. 🛠️ **Tool**: Version fingerprinting.

Q8Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: Yes! Upgrade to **Dgraph 25.3.1** or later. 📥 **Action**: Patch immediately via official release.

Q9What if no patch? (Workaround)

🚧 **No Patch?**: Block external access to `restoreTenant`. 🔒 **Mitigate**: Enforce strict API gateway auth. 🛑 **Isolate**: Network segmentation.

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: CRITICAL. 🚨 **Priority**: P1. 🏃 **Action**: Patch NOW. CVSS is High/HIGH/HIGH. Zero-day risk!

Continue exploring

Vulnerability detail Full AI analysis (login) dgraph-io CWE-862