Exploited CVEs / Langflow / CVE-2026-0770
CVE-2026-0770
Langflow Inclusion of Functionality from Untrusted Control Sphere Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-07-24 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.
Risk summary
Actively exploited Langflow vulnerability, Critical severity, CVSS 9.8. Added to the CISA KEV catalog 2026-07-21.
Senserva AI Opinion for CVE-2026-0770
CVE-2026-0770 lets remote attackers run arbitrary code on Langflow by pulling functionality from an untrusted control sphere, and it carries a Critical severity rating with a CVSS score of 9.8. CISA confirmed active exploitation and added it to the KEV catalog on 2026-07-21, with EPSS estimating a 53 percent exploit probability. Anyone running Langflow reachable from the network, especially internet-exposed instances used for building LLM workflows, is directly at risk of full compromise.
Do this: Identify every Langflow deployment, take internet-facing instances offline or restrict access immediately, and apply the vendor's patched version today.
AI-generated from public data, 2026-07-25. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-0770
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Updated August 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Full tracking and change history for CVE-2026-0770
- Published
- 2026-07-21
- Last revised
- 2026-07-21
- Changes tracked
- 1
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
The strongest signal is the July 21, 2026 addition to the CISA KEV catalog, confirming active exploitation before Severity was even scored to 9.8 on July 23, 2026. EPSS opened at 54.5% that same day, dipped to 53.5% on July 24, then climbed to 56.3% by July 28 and 56.9% by August 11. The trend is upward, so prioritize patching today.
Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.
- 2026-07-21 added to the CISA KEV catalog by CISA
- 2026-07-23 CVSS 0.0 to 9.8; EPSS first scored at 54.5%
- 2026-07-24 EPSS 54.5% to 53.5%
- 2026-07-28 EPSS 53.5% to 56.3%
- 2026-08-11 EPSS 56.3% to 56.9%
Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.
CISA required action
Federal (BOD 22-01) remediation due date: 2026-07-24 (past due).
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Official fix for CVE-2026-0770
Check the vendor's security advisory channel for the patched Langflow versions and workarounds.
Common questions about CVE-2026-0770
Is CVE-2026-0770 actively exploited?
Yes. CVE-2026-0770 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-07-21, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 57%.
What is the CISA deadline and required action for CVE-2026-0770?
CISA set the federal (BOD 22-01) remediation due date at 2026-07-24, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
What fixes CVE-2026-0770?
Check the vendor's security advisory for the patched Langflow versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2026-0770?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-0770's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).
Scope and sources
- More exploited Langflow CVEs
All Langflow exploited CVEs on one page: Langflow vulnerabilities actively exploited.
- Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.