ZIP Archive Path Traversal in IBM Langflow OSS
IBM Langflow OSS versions 1.0.0 through 1.12.3 allow an authenticated attacker to generate a server-produced ZIP archive containing path-traversal entries. If a victim extracts the archive with a tool that does not sanitize entry paths, files can be written outside the intended extraction directory on the victim's host. The vulnerability affects archive generation; the resulting arbitrary file write occurs during subsequent extraction.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can create or overwrite files outside the intended extraction directory on the victim's host, subject to the extracting user's filesystem permissions. This can compromise file integrity. Extraction with an unsafe tool is required; archive generation alone does not cause the victim-side file write.
If you can’t patch tonight, do this now.
No vendor-provided workaround is identified. As a precaution, avoid extracting untrusted Langflow-generated ZIP archives, or use an extraction tool that validates entry paths and prevents writes outside the intended extraction directory. Extracting with minimal filesystem privileges can limit the consequences of an unsafe extraction.
Patch, then assume compromise.
Upgrade IBM Langflow OSS to version 1.12.4. Back up the existing installation, review upgrade preparation instructions and release-specific configuration changes, perform the upgrade, and test existing flows.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.