CVE-2026-55255 · Published 23 Jun 2026
Langflow Langflow
On CISA's KEV list 14 days after disclosure; 1 public exploit.
Langflow contains an authorization bypass through user-controlled key vulnerability which allows an authenticated attacker to execute any flow belonging to another user by specifying the victim's flow ID in the request.
CISA required action (federal due date 10 Jul 2026): 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.
Signals
- KEV, exploited in the wild
- yes, added 7 Jul 2026, due 10 Jul 2026
- EPSS, 30-day forecast
- 0.9%, 60th percentile (as of 18 Nov 2026)
- CVSS, NVD
- not stated
- Internet exposure
- not stated
KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.
Timeline 23 Jun 2026 to today
- Disclosed
- First PoC+7 d
- KEV+7 d
7 days from disclosure to the first proof of concept
Indicators none tied yet
No threat feed has tied an indicator to this CVE yet. Checked every six hours.
On the wire 0 dispatches
No dispatch on our wire has named this CVE yet.
Public exploit code 1 known · links only
GitHub PoCs 1Metasploit 0Exploit-DB 0
GitHub PoCs, by trust then stars1
- rootdirective-sec/CVE-2026-55255-LabTrust ok 1000 stars
created 30 Jun 2026
Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.