CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Called exploited 3 days after 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 listing3d
- Last KEV listing11d
- Last sighting52d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Jul 7, 2026
- EUVDENISA, European Unionlisted Jul 7, 2026
- VulnCheck KEVcommercial researchlisted Jun 26, 2026
- CIRCLaggregator, mirrors the abovelisted Jul 7, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationwww.vulncheck.com/blog/pwning-the-ai-stack
- reported exploitationexpel.com/blog/the-ai-cve-exploitation-evidence-story-headli
- reported exploitationwww.acn.gov.it/portale/documents/20119/1300791/Operational_S
- reported exploitationwww.recordedfuture.com/blog/july-2026-cve-landscape
- reported exploitationwww.resecurity.com/es/blog/article/exploiting-langflows-vali
- reported exploitationprevidian.com/CVE-2026-55255
8 public reports collected from VulnCheck and CIRCL, first on Jun 26, 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. Prior to 1.9.1, an Insecure Direct Object Reference (IDOR) vulnerability in /api/v1/responses endpoint allows an authenticated attacker to execute any flow belonging to another user by specifying the victim's flow ID in the request. This vulnerability is fixed in 1.9.1.
Required action (CISA)
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.




