CVE-2026-9138: Langflow is vulnerable to arbitrary file write and arbitrary file deletion due to unvalidated paths in file-processing components

Published Aug 28, 2026
·
Updated

IBM Langflow OSS 1.0.0 through 1.11.2 Langflow could allow an authenticated attacker to write arbitrary files to the server due to improper input validation in the SaveToFileComponent. The application constructs local file paths using attacker‑controlled input without sufficient sanitization when handling requests to the /api/v1/run/{flowid} endpoint. An attacker with low‑privileged authenticated access (such as a valid API key or user session) can supply crafted path values, including absolute paths or path traversal sequences, allowing arbitrary file writes to locations writable by the Langflow process. Successful exploitation may lead to unauthorized file creation or modification, potentially resulting in further compromise depending on the deployment environment.

Affected Software

2 affected components
IBM Langflow OSS>=1.0.0<=1.11.2
IBM Langflow OSS<=1.0.0-1.11.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade IBM Langflow OSS to a version that resolves this vulnerability.

    Fixed in 1.11.3
  2. Compensating control

    If immediate upgrade to Langflow OSS 1.11.3 is not possible, restrict network access to the /api/v1/run/{flow_id} endpoint (e.g., via firewall/ACL/WAF) to reduce exposure of the vulnerable request path handling.

Event History

Aug 28, 2026
CVE Published
via IBM·12:00 AM
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Sep 4, 2026
CVE Published
via MITRE·02:27 PM
Data Sourced
via MITRE·02:27 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·03:17 PM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

Which deployments are affected?

IBM Langflow OSS versions 1.0.0 through 1.11.2 are identified as affected. Exposure applies where the Langflow process can write to filesystem locations targeted through crafted path input.

2

What level of access does an attacker need?

An attacker needs low-privileged authenticated access, such as a valid API key or an authenticated user session. No user interaction is required.

3

How is the vulnerable functionality reached?

The issue is triggered through requests to the /api/v1/run/{flow_id} endpoint involving the SaveToFileComponent. Crafted absolute paths or path-traversal sequences can influence the local file path used by the application.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203