Exploited CVEs / Langflow / CVE-2026-33017

CVE-2026-33017

Langflow Code Injection Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-04-08 (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

CriticalCISA KEV
9.8
CVSS v3 base
96%
EPSS exploit probability
Critical
Severity
2026-03-25
Added to KEV
2026-04-08 (past due)
CISA due date

Actively exploited Langflow vulnerability, Critical severity, CVSS v3 9.8. Added to the CISA KEV catalog 2026-03-25.

Senserva AI read on CVE-2026-33017CISA required actionOfficial fix for CVE-2026-33017What the press saysAdmin questions

Senserva AI Opinion for CVE-2026-33017

This Langflow flaw lets an unauthenticated attacker inject code by building public flows without logging in, meaning anyone who can reach your Langflow instance can run code on it. It carries Severity Critical (CVSS 9.8), sits on the CISA KEV list as confirmed exploited since 2026-03-25, and has a 100% EPSS score, so exposed instances are being hit now rather than as a hypothetical. Teams running Langflow reachable from untrusted networks are the ones at direct risk.

Do this: Locate every Langflow instance, restrict or block external access immediately, and apply the vendor fix before returning it to service.

AI-generated from public data, 2026-07-25. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-33017

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Federal remediation deadline 2026-04-08; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 23, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2026-33017

Published
2026-03-25
Last revised
2026-03-25
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.

Senserva Watchevery change we have recorded for this one
What changed, and when
0%25%50%75%100%CISA KEVCISA KEV on 2026-03-252026-07-17: EPSS 98%2026-07-17: EPSS 98%2026-07-24: EPSS 100%2026-07-24: EPSS 100%2026-07-30: EPSS 100%2026-07-30: EPSS 100%2026-08-12: EPSS 96%EPSS 96%2026-03-252026-08-12

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

  • 2026-03-25 added to the CISA KEV catalog by CISA
  • 2026-07-17 CVSS 0.0 to 9.8; EPSS first scored at 98.2%
  • 2026-07-24 EPSS 98.2% to 99.8%
  • 2026-07-30 EPSS 99.8% to 99.8%
  • 2026-08-12 EPSS 99.8% to 96.2%

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.

What the press says about CVE-2026-33017

Trusted-source coverage, pulled live from their own feeds.

“The Agentic AI threat cluster: Seven incidents, three actors, and what they mean for your exposure” Tenable, 2026-08-15
“Metasploit Wrap Up: Lot of summer shells and fit http profiles” Rapid7, 2026-08-14

CISA required action

Federal (BOD 22-01) remediation due date: 2026-04-08 (past due).

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Official fix for CVE-2026-33017

Check the vendor's security advisory channel for the patched Langflow versions and workarounds.

Common questions about CVE-2026-33017

Is CVE-2026-33017 actively exploited?

Yes. CVE-2026-33017 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-03-25, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 96%.

What is the CISA deadline and required action for CVE-2026-33017?

CISA set the federal (BOD 22-01) remediation due date at 2026-04-08, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

What fixes CVE-2026-33017?

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-33017?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-33017'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.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.