Unauthenticated code execution via unsafe Python evaluation
Published Jan 23, 2026 · Updated Jan 23, 2026
Eval injection in Langflow OSS 1.3.2 allows remote attackers to execute arbitrary code through a crafted network request. The eval_custom_component_code function fails to validate a user-supplied string before passing it to Python code execution in the Langflow process. Authentication and user interaction are not required, and successful exploitation runs code with the permissions of the current Langflow process.
Summary
What happened
Eval injection in Langflow OSS 1.3.2 allows remote attackers to execute arbitrary code through a crafted network request. The eval_custom_component_code function fails to validate a user-supplied string before passing it to Python code execution in the Langflow process. Authentication and user interaction are not required, and successful exploitation runs code with the permissions of the current Langflow process.
The record
- CVE
- CVE-2026-0769
- Published
- Jan 23, 2026
- Updated
- Jan 23, 2026
- Vendor
- OpenBMC Project
- Product
- Langflow OSS
- Classifications
- CWE-95, T1190, T1059.006
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2026CVE publishedPublication date reported by the CVE source.
- Jan 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.3.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
No public exploit references are available in this record.
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