Called exploited 22 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 listing22d
- Last KEV listing5mo
- Last sighting38d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Jul 21, 2026
- EUVDENISA, European Unionlisted Jul 21, 2026
- VulnCheck KEVcommercial researchlisted Feb 14, 2026
- CIRCLaggregator, mirrors the abovelisted Jul 21, 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 exploitationblog.previdian.com/cve-2026-0770-exploited-in-the-wild-langf
10 public reports collected from VulnCheck and CIRCL, first on Feb 14, 2026. Each links to its original source. We have not verified them.
Description
Langflow contains an inclusion of functionality from untrusted control sphere vulnerability that allows remote attackers to execute arbitrary code on affected installations.
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.
