Arbitrary file read via TAR symlink extraction
Published Jun 23, 2026 · Updated Jun 23, 2026
Arbitrary file read in Langflow OSS before 1.9.2 allows remote attackers to expose host files through crafted TAR uploads. BaseFileComponent._unpack_bundle extracts symbolic links, and process_files follows them with path.read_bytes() while ingesting their targets into RAG storage. Exploitation requires an affected flow to ingest the attacker-controlled archive; disclosed files can include the JWT signing key, enabling forged access and code execution.
Summary
What happened
Arbitrary file read in Langflow OSS before 1.9.2 allows remote attackers to expose host files through crafted TAR uploads. BaseFileComponent._unpack_bundle extracts symbolic links, and process_files follows them with path.read_bytes() while ingesting their targets into RAG storage. Exploitation requires an affected flow to ingest the attacker-controlled archive; disclosed files can include the JWT signing key, enabling forged access and code execution.
The record
- CVE
- CVE-2026-55447
- Published
- Jun 23, 2026
- Updated
- Jun 23, 2026
- Vendor
- OpenBMC Project
- Product
- Langflow OSS
- Classifications
- CWE-61, CWE-200, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 23, 2026CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.9.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- BaseFileComponent TAR symlink proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo