CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Called exploited 1 days before disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listing1d
- Last KEV listing6d
- Last sighting5mo
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Mar 25, 2026
- EUVDENISA, European Unionlisted Mar 25, 2026
- VulnCheck KEVcommercial researchlisted Mar 19, 2026
- CIRCLaggregator, mirrors the abovelisted Mar 25, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationwww.akamai.com/blog/security-research/2026/sep/analyzing-go-
- reported exploitationwww.vulncheck.com/blog/pwning-the-ai-stack
- reported exploitationexpel.com/blog/the-ai-cve-exploitation-evidence-story-headli
- reported exploitationwww.tenable.com/blog/the-agentic-ai-threat-cluster-seven-inc
- reported exploitationunit42.paloaltonetworks.com/autonomous-ai-cyber-attack-campa
- reported exploitationwww.resecurity.com/es/blog/article/exploiting-langflows-vali
16 public reports collected from VulnCheck and CIRCL, first on Mar 19, 2026. Each links to its original source. We have not verified them.
Description
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 pu
Required action (CISA)
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.






