Q: Who is affected? (Versions/Components)

👥 **Affected**: **Langflow** versions **prior to 1.9.0**. 📦 **Component**: Specifically the **GitHub Actions workflows** used in the development/CI pipeline, not necessarily the runtime app itself.

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

⚡ **Exploitation Threshold**: **LOW**. 🚫 **Auth**: **Unauthenticated** (PR:N). 🌐 **Access**: **Network** (AV:N). 🖱️ **UI**: **None required** (UI:N). Easy to exploit remotely.

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

💣 **Public Exploit**: **No** public PoC or wild exploitation detected yet. 📝 **Status**: POCs list is empty in the advisory. However, the CVSS score suggests it is highly exploitable if discovered.

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

🔍 **Self-Check**: Scan your GitHub repository for **Langflow workflows**. 🧐 Look for **unvalidated inputs** passed to shell commands in `.github/workflows/`. 🛠️ Use SAST tools to detect **CWE-74** patterns in CI scripts.

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

✅ **Official Fix**: **Yes**. Upgrade to **Langflow 1.9.0** or later. 📢 **Reference**: See GitHub Security Advisory **GHSA-87cc-65ph-2j4w** for details on the patch.

Q: Is it urgent? (Priority Suggestion)

🔥 **Urgency**: **HIGH**. 📅 **Priority**: Patch immediately. With **CVSS 8.6** (High) and **unauthenticated** access, this is a critical risk for CI/CD pipelines. Don't wait for a PoC! 🏃♂️

Question 1

What is this vulnerability? (Essence + Consequences)

Accepted Answer

🚨 **Essence**: Langflow < 1.9.0 has a **Remote Shell Injection** flaw in GitHub Actions workflows.…

Question 2

Root Cause? (CWE/Flaw)

Accepted Answer

🛡️ **Root Cause**: **CWE-74** (OS Command Injection). The vulnerability stems from **unauthenticated remote shell injection** within multiple GitHub Actions workflows.…

Question 3

Who is affected? (Versions/Components)

Accepted Answer

👥 **Affected**: **Langflow** versions **prior to 1.9.0**. 📦 **Component**: Specifically the **GitHub Actions workflows** used in the development/CI pipeline, not necessarily the runtime app itself.

Question 4

What can hackers do? (Privileges/Data)

Accepted Answer

🕵️ **Attacker Capabilities**: Full **OS command execution**. 📂 **Impact**: Can steal **secrets** (API keys, tokens) and **manipulate infrastructure** (modify files, install backdoors).…

Question 5

Is exploitation threshold high? (Auth/Config)

Accepted Answer

⚡ **Exploitation Threshold**: **LOW**. 🚫 **Auth**: **Unauthenticated** (PR:N). 🌐 **Access**: **Network** (AV:N). 🖱️ **UI**: **None required** (UI:N). Easy to exploit remotely.

Question 6

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

Accepted Answer

💣 **Public Exploit**: **No** public PoC or wild exploitation detected yet. 📝 **Status**: POCs list is empty in the advisory. However, the CVSS score suggests it is highly exploitable if discovered.

Question 7

How to self-check? (Features/Scanning)

Accepted Answer

🔍 **Self-Check**: Scan your GitHub repository for **Langflow workflows**. 🧐 Look for **unvalidated inputs** passed to shell commands in `.github/workflows/`. 🛠️ Use SAST tools to detect **CWE-74** patterns in CI scripts.

Question 8

Is it fixed officially? (Patch/Mitigation)

Accepted Answer

✅ **Official Fix**: **Yes**. Upgrade to **Langflow 1.9.0** or later. 📢 **Reference**: See GitHub Security Advisory **GHSA-87cc-65ph-2j4w** for details on the patch.

Question 9

What if no patch? (Workaround)

Accepted Answer

🚧 **No Patch Workaround**: If stuck on old versions, **restrict GitHub Actions permissions**. 🔒 Disable unnecessary workflow triggers.…

Question 10

Is it urgent? (Priority Suggestion)

Accepted Answer

🔥 **Urgency**: **HIGH**. 📅 **Priority**: Patch immediately. With **CVSS 8.6** (High) and **unauthenticated** access, this is a critical risk for CI/CD pipelines. Don't wait for a PoC! 🏃‍♂️

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

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