Q: Who is affected? (Versions/Components)

🏢 **Vendor**: LXC (Incus). 📦 **Product**: Incus. ⚠️ **Affected**: Versions **prior to 6.23.0**. If you are running 6.22.x or older, you are vulnerable!

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

💀 **Privileges**: Escalates from container user to **Host Root**. 📂 **Data**: Full **arbitrary read/write** capabilities. Hackers can steal data, modify system files, or pivot to other containers. Total compromise!

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

🔑 **Auth**: Requires **Low Privileges** (PR:L). 🌐 **Network**: Attackable over **Network** (AV:N). 🚫 **UI**: No User Interaction needed (UI:N). Threshold is **LOW** for authenticated users.

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

📜 **Public Exp**: No PoC provided in data. 🌍 **Wild Exp**: Unconfirmed. However, the CVSS score is **Critical (9.8)**, implying high exploitability potential once discovered. Stay alert!

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

🔍 **Check**: Scan for Incus version < 6.23.0. 📝 **Feature**: Look for custom **instance templates** using pongo2 syntax. If templates are user-controllable, risk is HIGH.

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

✅ **Fixed**: Yes! Upgrade to **Incus 6.23.0** or later. 📥 **Patch**: Official advisory available at GitHub Security Advisories (GHSA-83xr-5xxr-mh92).

Q: What if no patch? (Workaround)

🚧 **Workaround**: If patching is delayed, **restrict template creation** to trusted admins only. 🛑 **Disable** user-defined pongo2 templates in instance configs until upgraded.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **CRITICAL**. CVSS 9.8 means immediate action required. 🏃 **Action**: Patch to v6.23.0 **NOW**. Do not wait for an exploit to appear!

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: Incus < 6.23.0 has a **template bypass** flaw. 📉 **Consequences**: Attackers can escape **chroot isolation**, leading to **arbitrary read/write** access on the host system. Critical integrity loss!

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **CWE**: CWE-1336 (Improper Handling of Insufficiently Specified Resource).…

Question 3

Who is affected? (Versions/Components)

Accepted Answer

🏢 **Vendor**: LXC (Incus). 📦 **Product**: Incus. ⚠️ **Affected**: Versions **prior to 6.23.0**. If you are running 6.22.x or older, you are vulnerable!

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

💀 **Privileges**: Escalates from container user to **Host Root**. 📂 **Data**: Full **arbitrary read/write** capabilities. Hackers can steal data, modify system files, or pivot to other containers. Total compromise!

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

🔑 **Auth**: Requires **Low Privileges** (PR:L). 🌐 **Network**: Attackable over **Network** (AV:N). 🚫 **UI**: No User Interaction needed (UI:N). Threshold is **LOW** for authenticated users.

Question 6

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

Accepted Answer

📜 **Public Exp**: No PoC provided in data. 🌍 **Wild Exp**: Unconfirmed. However, the CVSS score is **Critical (9.8)**, implying high exploitability potential once discovered. Stay alert!

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Check**: Scan for Incus version < 6.23.0. 📝 **Feature**: Look for custom **instance templates** using pongo2 syntax. If templates are user-controllable, risk is HIGH.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

✅ **Fixed**: Yes! Upgrade to **Incus 6.23.0** or later. 📥 **Patch**: Official advisory available at GitHub Security Advisories (GHSA-83xr-5xxr-mh92).

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **Workaround**: If patching is delayed, **restrict template creation** to trusted admins only. 🛑 **Disable** user-defined pongo2 templates in instance configs until upgraded.

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **CRITICAL**. CVSS 9.8 means immediate action required. 🏃 **Action**: Patch to v6.23.0 **NOW**. Do not wait for an exploit to appear!

Goal Reached Thanks to every supporter — we hit 100%!

CVE-2026-33897 — AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

Q2Root Cause? (CWE/Flaw)

Q3Who is affected? (Versions/Components)

Q4What can hackers do? (Privileges/Data)

Q5Is exploitation threshold high? (Auth/Config)

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

Q7How to self-check? (Features/Scanning)

Q8Is it fixed officially? (Patch/Mitigation)

Q9What if no patch? (Workaround)

Q10Is it urgent? (Priority Suggestion)

Continue exploring