Threadlinqs IntelligenceStart free

Vendor1 product tracked

Langflow vulnerabilities & exploitation

4 in CISA KEV2 ransomware-linked5 with public exploit

As of 2026-10-20, Threadlinqs tracks 5 Langflow CVEs, 4 in the CISA Known Exploited Vulnerabilities catalog, 2 used in ransomware campaigns, linked to 22 tracked threat campaigns and 6 named threat actors.

CVEs
5Since 2025
CISA KEV
480% of CVEs
Critical
4CVSS v3 9.0+
Avg CVSS
9.6/10Max 9.8
Threats
22Linked campaigns
Actors
6Named in campaigns

Data as of:

Exploitation timeline

Threadlinqs has recorded 5 Langflow CVEs published between and . The busiest month was 2026-01 (2 new CVEs). 4 of them (80%) are listed in CISA KEV, which means exploitation in the wild has been confirmed.

Most exploited vulnerabilities

Ranked with CISA KEV listings first, then EPSS exploit probability, then CVSS score. Showing 5 of 5 tracked Langflow CVEs.

Products affected

Threadlinqs normalises CPE and CNA product records across all 5 CVEs; 1 distinct Langflow product is affected. The most frequently affected:

  • Langflow 5 CVEs

Threat activity

22 tracked threat campaigns reference Langflow products or exploit Langflow CVEs:

Threat actors targeting Langflow

Named threat actors attributed to campaigns that involve Langflow products or CVEs, with the number of linked campaigns:

How to prioritise Langflow patching

This order follows the data Threadlinqs holds for Langflow, not a generic severity checklist:

  • 4 of 5 Langflow CVEs (80%) are in CISA KEV: treat them as actively exploited and remediate them first, starting with CVE-2025-3248, CVE-2025-34291, CVE-2026-0770.
  • 2 CVEs are known to be used in ransomware campaigns; patch these ahead of other KEV entries on internet-facing systems.
  • Outside KEV, the highest EPSS scores are CVE-2026-0768 (23.2%).
  • 4 CVEs score Critical and 1 High on CVSS v3 (maximum 9.8, average 9.6); sequence these after KEV and high-EPSS items.
  • 5 CVEs have a public exploit or proof of concept recorded, which shortens the time from disclosure to attack.

About this data

Vendor attribution comes from the CNA and CPE product records of each CVE, folded to one vendor name; CVSS, EPSS and KEV status are read from the Threadlinqs CVE catalog; campaign and actor links come from tracked threat records. Counts reflect the data as of 2026-10-20 and refresh daily.