Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: WeKnora (Tencent's LLM framework) suffers from **OS Command Injection**.…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: **CWE-78** (OS Command Injection).
🔍 **Flaw**: The **MCP stdio configuration validation** is flawed. It fails to properly sanitize inputs before passing them to the OS shell.

Question 3

Who is affected? (Versions/Components)

Accepted Answer

📦 **Affected**: **Tencent WeKnora**.
📅 **Versions**: **0.2.5 through 0.2.10** (prior to 0.2.10).
🏢 **Vendor**: Tencent.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

💀 **Attacker Actions**:
✅ **Arbitrary Command Execution**: Run any OS command.
🔓 **Privileges**: Gain the same privileges as the WeKnora process.…

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

⚠️ **Threshold**: **Low** for Auth, **Medium** for Config.
🔑 **Auth**: Requires **Low Privileges** (PR:L).
⚙️ **Config**: Requires interaction with **MCP stdio configuration**.…

Question 6

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

Accepted Answer

🚫 **Public Exploit**: **No**.
📄 **PoC**: The `pocs` field is empty in the advisory.
📢 **Status**: No wild exploitation reported yet, but the flaw is critical.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**:
1. Check WeKnora version (0.2.5-0.2.10).
2. Review **MCP stdio** configuration inputs.
3. Scan for shell metacharacters (`;`, `|`, `$()`) in config files.
4.…

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

✅ **Fixed**: **Yes**.
📅 **Published**: 2026-03-07.
🔗 **Advisory**: [GitHub Advisory GHSA-r55h-3rwj-hcmg](https://github.com/Tencent/WeKnora/security/advisories/GHSA-r55h-3rwj-hcmg).…

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch Workaround**:
1. **Disable MCP stdio** if not needed.
2. **Strict Input Validation**: Sanitize all config inputs to remove shell metacharacters.
3.…

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **CRITICAL**.
📊 **CVSS**: **9.8** (High).
⚡ **Priority**: **Immediate Patching**.
📉 **Risk**: High impact (Confidentiality, Integrity, Availability) with low exploitation difficulty.

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

CVE-2026-30861 — 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