CVE-2026-33309
Versions 1.2.0 through 1.8.1 have a bypass of the patch for CVE-2025-68478 (External Control of File Name), leading to the root architectural issue within `LocalStorageService` remaining unresolved.
Does this matter?
EPSS puts the probability of exploitation in the next 30 days at 11.1%, higher than 96% of all known CVEs. Patch or mitigate before the next change window.
Description
Langflow is a tool for building and deploying AI-powered agents and workflows. Versions 1.2.0 through 1.8.1 have a bypass of the patch for CVE-2025-68478 (External Control of File Name), leading to the root architectural issue within `LocalStorageService` remaining unresolved. Because the underlying storage layer lacks boundary containment checks, the system relies entirely on the HTTP-layer `ValidatedFileName` dependency. This defense-in-depth failure leaves the `POST /api/v2/files/` endpoint vulnerable to Arbitrary File Write. The multipart upload filename bypasses the path-parameter guard, allowing authenticated attackers to write files anywhere on the host system, leading to Remote Code Execution (RCE). Version 1.9.0 contains an updated fix.
- CVSS 3.1
- 9.9 CRITICALCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- EPSS
- 11.06% probability · 96th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-22, CWE-73, CWE-94, CWE-284
- Affected
- langflow/langflow
- Source
- security-advisories@github.com
References
- https://github.com/langflow-ai/langflow/security/advisories/GHSA-g2j9-7rj2-gm6cExploit, Mitigation, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.