CVE-2026-25643 — AI Deep Analysis Summary

Q: Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-78** (OS Command Injection). 🐛 **Flaw**: User inputs in video stream configurations are **not sanitized** before being passed to the `exec` instruction.

Q: Who is affected? (Versions/Components)

📦 **Affected**: **Frigate** by Blake Blackshear. 📉 **Versions**: All versions **prior to 0.16.4** (i.e., ≤ 0.16.3).

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

💀 **Capabilities**: Hackers gain **Remote Command Execution**. 📊 **Impact**: High severity (CVSS 9.8). They can read, modify, or delete data, and escalate privileges to root/admin level.

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

🔐 **Threshold**: **Medium**. ⚠️ **Auth**: Requires **High Privileges** (PR:H) to configure streams. 🌐 **Access**: Network accessible (AV:N).

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

🔍 **Exploits**: **Yes**, public PoCs exist. 📂 **Links**: GitHub repos by `jduardo2704` and `joshuavanderpoll` demonstrate blind RCE via go2rtc exec injection.

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

🔎 **Check**: Look for Frigate versions **< 0.16.4**. 📝 **Config**: Check `config.yaml` for custom video stream inputs that might contain unsanitized user data.

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

✅ **Fixed**: **Yes**. 🛠️ **Patch**: Upgrade to **Frigate v0.16.4** or later. 📢 **Advisory**: See GitHub Security Advisory GHSA-4c97-5jmr-8f6x.

Q: What if no patch? (Workaround)

🚧 **Workaround**: If unpatched, **restrict network access** to the NVR. 🚫 **Mitigation**: Do not allow untrusted users to modify video stream configurations.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **Critical**. 🚀 **Priority**: Patch immediately. The CVSS score is **9.8** (Critical), and public exploits are available.

Updated May 06, 2026 CVSS 9.1 · 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**: Frigate NVR allows **Remote Code Execution (RCE)** via command injection.…

Read full answer (login)

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-78** (OS Command Injection). 🐛 **Flaw**: User inputs in video stream configurations are **not sanitized** before being passed to the `exec` instruction.

Q3Who is affected? (Versions/Components)

📦 **Affected**: **Frigate** by Blake Blackshear. 📉 **Versions**: All versions **prior to 0.16.4** (i.e., ≤ 0.16.3).

Q4What can hackers do? (Privileges/Data)

💀 **Capabilities**: Hackers gain **Remote Command Execution**. 📊 **Impact**: High severity (CVSS 9.8). They can read, modify, or delete data, and escalate privileges to root/admin level.

Q5Is exploitation threshold high? (Auth/Config)

🔐 **Threshold**: **Medium**. ⚠️ **Auth**: Requires **High Privileges** (PR:H) to configure streams. 🌐 **Access**: Network accessible (AV:N).

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

🔍 **Exploits**: **Yes**, public PoCs exist. 📂 **Links**: GitHub repos by `jduardo2704` and `joshuavanderpoll` demonstrate blind RCE via go2rtc exec injection.

Q7How to self-check? (Features/Scanning)

🔎 **Check**: Look for Frigate versions **< 0.16.4**. 📝 **Config**: Check `config.yaml` for custom video stream inputs that might contain unsanitized user data.

Q8Is it fixed officially? (Patch/Mitigation)

✅ **Fixed**: **Yes**. 🛠️ **Patch**: Upgrade to **Frigate v0.16.4** or later. 📢 **Advisory**: See GitHub Security Advisory GHSA-4c97-5jmr-8f6x.

Q9What if no patch? (Workaround)

🚧 **Workaround**: If unpatched, **restrict network access** to the NVR. 🚫 **Mitigation**: Do not allow untrusted users to modify video stream configurations.

Q10Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **Critical**. 🚀 **Priority**: Patch immediately. The CVSS score is **9.8** (Critical), and public exploits are available.

Continue exploring

Vulnerability detail Full AI analysis (login) blakeblackshear CWE-78