CVE-2026-6542

CVE-2026-6542 is a medium-severity vulnerability in Langflow with a CVSS 3.x base score of 6.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-639.

Key facts

Description

IBM Langflow OSS 1.0.0 through 1.8.4 could allow any user to supply a flow_id to read transaction logs and vertex build data belonging to other users, and to delete persisted vertex build data for another user's flow.

Frequently asked questions

What is CVE-2026-6542?
IBM Langflow OSS 1.0.0 through 1.8.4 could allow any user to supply a flow_id to read transaction logs and vertex build data belonging to other users, and to delete persisted vertex build data for another user's flow.
How severe is CVE-2026-6542?
CVE-2026-6542 has a CVSS 3.x base score of 6.5, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-6542 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-6542?
CVE-2026-6542 affects Langflow. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-6542?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-6542 have an EU (EUVD) identifier?
Yes. CVE-2026-6542 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-26447.
When was CVE-2026-6542 published?
CVE-2026-6542 was published on 2026-04-30 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Langflow

All CVEs affecting Langflow →

Other CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities

Browse all CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities →