Attackers Exploit Critical Langflow and Ruby on Rails Flaws for Credential Theft and C2 Infrastructure
Security researchers have confirmed active exploitation of two critical vulnerabilities: CVE-2026-0768 affecting Langflow and CVE-2026-66066 (nicknamed KindaRails2Shell) in Ruby on Rails. The campaigns follow a clear pattern of initial reconnaissance and secret theft followed by efforts to establish command-and-control infrastructure, raising the risk of eventual remote code execution.
In Langflow, the flaw permits arbitrary Python code execution with root privileges because of inadequate input validation. Observed requests target environment variables such as LANGFLOW_SUPERUSER, patterns matching OPENAI_API keys, and AWS credentials including AWS_ACCESS and AWS_SECRET. Attackers have also attempted to read sensitive paths such as /root/.cache/langflow/secret_key and inspected local artifacts including .ssh directories and the size of .bash_history files.
The Ruby on Rails vulnerability is particularly concerning because it can be chained to achieve remote code execution. CVE-2026-66066 originates from an arbitrary file-read condition that activates when Active Storage processes image uploads using the libvips library. Exploitation requires that the application uses Vips as the variant processor and accepts image uploads from untrusted users. The root cause lies in discrepancies between how Active Storage interprets files and how libvips processes them, potentially leaking secrets used by Rails to protect sessions and encrypt data.
Recoverable secrets include secret_key_base, the Rails master key, database credentials, cloud storage keys, and external service tokens. With these materials an attacker can move from file reads to code execution, pivot across systems, and maintain persistence without valid credentials.
Indicators point to a distributed campaign. Langflow traffic has been linked primarily to Russian origins with confirmed impact on canary instances in the United Kingdom. For Rails, activity has been observed against canaries in Singapore, Israel, and the United Kingdom, with C2 communications directed toward a host in Israel from a single IP located in France.
Recommended defensive actions include identifying publicly exposed Langflow instances and Rails applications that use Active Storage with image uploads. For Rails, the primary mitigation is to update to versions 7.2.3.2, 8.0.5.1, or 8.1.3.1 and review the ruby-vips and libvips chain to block unsafe operations on untrusted content. If patching is delayed, organizations should disable Vips processing or restrict image uploads. Because the focus is on secrets, immediate rotation of secret_key_base, the master key, and any associated cloud, database, or API credentials is advised. Logs should be reviewed for suspicious reads of paths such as /proc/self/environ and config/master.key, while detection rules for C2 traffic should be strengthened.
Related articles
Enodia: Open-Source Go Tool Automates Service Inventory, EOL Tracking and CVE Correlation
A DevOps engineer has released enodia, a single-binary Go CLI that discovers real versions of services across large heterogeneous environments and correlates them with end-of-life calendars and vulnerability databases. The tool was built after manual Ansible-based inventories and existing solutions such as endoflife.date, nvchecker, Renovate and Uptime Kuma proved insufficient for covering both infrastructure and application services while also providing actionable lifecycle, patch and branch status. Enodia uses product-specific probes for 123 technologies including PostgreSQL, MySQL, MariaDB, Jira, Confluence, Bitbucket, VMware vCenter, ESXi, pfSense and multiple Linux distributions, falling back to a generic URL-plus-regex probe when needed. Data collection is deliberately separated from evaluation so that inventory.jsonl files can be generated inside air-gapped networks and later analysed where CVE feeds are available. The project also contributed dozens of missing products and corrected EOL dates to the endoflife.date project and integrates both NVD and Russia’s FSTEC BDU vulnerability databases. Special handling was added for MySQL/MariaDB connection-error counters, version-string masquerading, and vendor-specific update nomenclature to avoid false reports.
Telegram Voice Call Flaw Allows Remote Code Execution on Android Devices
Security researchers disclosed a vulnerability in Telegram for Android that enables remote code execution on a victim's device simply by answering a voice call. The attacker requires only a standard account, and the flaw was present in versions 8.6.2 through 12.10.3 released between March 2022 and September 2026. Telegram addressed the issue in version 12.10.4, released at the end of September 2026. The root cause lies in improper handling of the MediaState message exchanged during calls, specifically when processing rotation values and missing video state fields, leading to out-of-bounds memory reads. The same underlying fix was deployed earlier to shared call libraries, iOS, and desktop clients, but reached Android later. Researchers confirmed the impact only on private calls running on ARM64 Android devices, with no evidence of exploitation in the wild or public CVE assignment as of October 29, 2026.
360 Security Cloud Opens PHP2Shell Vulnerability Self-Check Platform to Government and Enterprise Users
360 Security Cloud has launched a dedicated self-assessment platform that allows organizations to scan their PHP-based websites and systems for the PHP2Shell vulnerability. The service is now available to government agencies, large enterprises, and small-to-medium businesses. Users can apply by scanning a provided QR code to determine how many of their assets run PHP, identify affected versions, and check whether any systems have already been compromised. The platform addresses key questions about exposure: the number of PHP-powered sites and systems, the presence of vulnerable versions, and signs of prior intrusion. The announcement emphasizes that the tool helps organizations proactively assess risk without requiring external assistance. The original Chinese report was published on October 30, 2026, and the service is positioned as a practical response to ongoing PHP-related security concerns.
Liferay Community Edition Misconfiguration Exposes Plaintext Passwords in Government Systems via CWE-319
A detailed analysis reveals how the use of Liferay Community Edition in a closed government information system led to the transmission of user passwords in plaintext through transactional emails. The issue stemmed from default notification templates that included the [$PASSWORD$] macro, combined with unadjusted system variables pointing to localhost instead of the production domain. Despite proper OAuth 2.0 delegation and CSRF protections, the misconfigured password change workflow sent permanent credentials in clear text to user inboxes. The root cause was traced to custom portlets that incorrectly reused the New Password Notification trigger intended only for administrator-initiated resets. Remediation involves removing the password macro from email templates and updating portal-ext.properties to enforce production host settings. The case highlights how open-source enterprise platforms require thorough hardening beyond initial code audits when deployed in high-security environments.