Critical Langflow RCE (CVE-2024-34200) Actively Exploited by Attackers

Key Takeaways

• Two critical vulnerabilities, CVE-2026-0768 in Langflow and CVE-2026-66066 in Ruby on Rails, are under active exploitation.
• Attackers are leveraging these flaws for reconnaissance, harvesting sensitive secrets, and potential remote code execution.
• The Langflow RCE allows unauthenticated code execution, while the Rails flaw enables file reading to RCE, facilitating credential theft.
• Both vulnerabilities have known fixes, and immediate patching and credential rotation are advised.

Critical Flaws in Langflow and Ruby on Rails Under Active Attack

Cybersecurity firm VulnCheck has reported active exploitation of two distinct, critical vulnerabilities affecting Langflow, an AI application development platform, and deployments utilizing Ruby on Rails. Attackers are swiftly moving from public disclosure to reconnaissance, secret exfiltration, and the potential for remote code execution (RCE), according to VulnCheck’s telemetry.

Unauthenticated RCE Hits Langflow

The first vulnerability, identified as CVE-2026-0768, impacts Langflow, a low-code platform designed for building AI-powered applications, agents, and workflow automations. VulnCheck’s internet-facing Canary systems detected exploitation attempts shortly after this flaw was added to its Known Exploited Vulnerabilities catalog.

CVE-2026-0768 is an unauthenticated RCE vulnerability residing within the code validator of Langflow’s custom component editor. This critical flaw allows an attacker to execute arbitrary code on a vulnerable server without requiring any prior authentication.

While the vulnerability was initially disclosed through Trend Micro’s Zero Day Initiative in January, VulnCheck said no public proof-of-concept exploit was known at the time its researchers observed these initial attacks. The company initially recorded over 50 detections, a number that subsequently surged to approximately 360 exploitation events. The observed malicious requests appeared to prioritize identifying valuable credentials and access pathways over immediately deploying destructive payloads like ransomware.

Attackers Target Secrets and Cloud Access

During the exploitation attempts, observed commands focused on retrieving environment variables associated with Langflow administration, OpenAI APIs, and Amazon Web Services (AWS) cloud access. Attackers also sought to read Langflow’s local secret key file located at /root/.cache/langflow/secret_key, inspect SSH access configurations, and determine the size of .bash_history files. These reconnaissance efforts could provide intruders with insights into administrator activity, stolen credentials, accessible cloud resources, and potential avenues for lateral movement within compromised networks.

VulnCheck said the Langflow traffic predominantly originated from Russia and, at the time of their report, targeted Canary systems situated in the United Kingdom. This activity underscores a growing trend of exploitation targeting Langflow, with several other related vulnerabilities reportedly added to VulnCheck’s KEV catalog throughout 2026.

Ruby on Rails Vulnerability Enables File-Read-to-RCE

Separately, researchers also observed active exploitation of CVE-2026-66066, a critical Ruby on Rails vulnerability. This flaw is described as an Active Storage file-read-to-RCE issue. Attacks leveraging this vulnerability impacted Canary systems located in Singapore, Israel, and the United Kingdom. VulnCheck traced this activity to a single source IP address in France, with command-and-control communications established with a host in Israel.

The Rails vulnerability is particularly dangerous because it allows an attacker to first use file-reading capabilities to obtain sensitive application secrets. These can include the secret_key_base, API tokens, database credentials, and cloud-storage keys. Such secrets can remain valuable to attackers even after the vulnerable software has been patched. For instance, a compromised Rails secret_key_base could enable session forgery or other abuses until it is rotated.

These incidents highlight how platforms for AI application development and widely deployed web frameworks are increasingly becoming high-value targets for threat actors.

What You Should Do

• Patch Immediately: Organizations running Langflow or Ruby on Rails should promptly identify all exposed instances and apply the latest vendor fixes.
• Restrict Access: Limit public access to administrative interfaces and critical components of these platforms.
• Review Logs: Scrutinize server logs for any unusual commands or activities targeting environment variables, secret files, SSH directories, or shell-history files.
• Rotate Credentials: If exploitation is suspected, immediately rotate all potentially compromised credentials, API keys, cloud secrets, and application signing keys.
• Assume Compromise: Treat any secrets accessible to a compromised application as potentially exposed and replace them, as patching alone may not mitigate the risk of stolen secrets.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.