Threat Intelligence / CVE / CVE-2026-33017

CVE-2026-33017 — Langflow

CISA KEV
CVSS v3.1 9.8 (CRITICAL) · CVSS v4.0 9.3 · EPSS 5.6% (higher than 90.3% of all scored CVEs) · Priority 9/10 · Published 2026-03-20

As of 2026-03-26, CVE-2026-33017 is a CRITICAL-severity vulnerability in Langflow, CVSS v3.1 9.8, EPSS 5.6% (90.3th percentile). It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-03-25), with a US federal remediation deadline of 2026-04-08. Threadlinqs Intelligence links 5 tracked threat campaigns to CVE-2026-33017, most recently “JADEPUFFER: AI Agent Exploits Langflow RCE (CVE-2025-3248) to Automate Database Ransomware/Extortion Attack”.

Last updated: 2026-03-26

What is CVE-2026-33017?

Langflow is a tool for building and deploying AI-powered agents and workflows. In versions prior to 1.9.0, the POST /api/v1/build_public_tmp/{flow_id}/flow endpoint allows building public flows without requiring authentication. When the optional data parameter is supplied, the endpoint uses attacker-controlled flow data (containing arbitrary Python code in node definitions) instead of the stored flow data from the database. This code is passed to exec() with zero sandboxing, resulting in unauthenticated remote code execution. This is distinct from CVE-2025-3248, which fixed /api/v1/validate/code by adding authentication. The build_public_tmp endpoint is designed to be unauthenticated (for public flows) but incorrectly accepts attacker-supplied flow data containing arbitrary executable code. This issue has been fixed in version 1.9.0.

The record classifies CVE-2026-33017 under weakness classes CWE-94, CWE-95, CWE-306. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 176 days ago.

Severity and exploitation probability

CVSS v3.1 base score
9.8 — CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0 base score
9.3
EPSS (FIRST)
5.6% probability of exploitation in the next 30 days, higher than 90.3% of all scored CVEs
CISA KEV
Listed since 2026-03-25, federal remediation deadline 2026-04-08
Threadlinqs priority
9/10 — CISA KEV-listed, which Threadlinqs floors at 9
Published
2026-03-20, last modified 2026-03-26

Is CVE-2026-33017 being exploited?

CISA added CVE-2026-33017 to the Known Exploited Vulnerabilities catalog on 2026-03-25, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2026-04-08 under BOD 22-01. It currently carries a trending score of 38 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-33017

The record marks a vendor fix as available for CVE-2026-33017. Vendor advisory: https://github.com/langflow-ai/langflow/commit/73b6612e3ef25fdae0a752d75b0fabd47328d4f0. Because CVE-2026-33017 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2026-04-08. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-33017

5 tracked threats in the Threadlinqs corpus reference CVE-2026-33017, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Seeded from threadlinqs-intel and not yet processed by the Threadlinqs enrichment pipeline, so blank CVSS, EPSS or KEV fields above mean NOT MEASURED rather than measured-absent.

Full detection coverage & IOCs for threats exploiting CVE-2026-33017 are available via the Threadlinqs MCP server (Purple tier). View plans →

← all vulnerabilities · Markdown version · Threadlinqs Intelligence