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
Code Signing Myths: Why a Valid Digital Signature Does Not Equal File Safety
Digital signatures confirm only that a file was issued by a specific publisher at a given time and remained unchanged afterward. They do not verify current safety, the legitimacy of the current holder, or whether the private key was stolen months earlier. Attackers obtain legitimate certificates through build-system leaks, supply-chain compromises such as the 2019 ASUS ShadowHammer incident, or weak reseller validation. Expired certificates remain usable because verification can be performed at the timestamp recorded by an RFC 3161 TSA token rather than the current system clock. Signature hashes in Authenticode deliberately exclude the checksum field, certificate table, and attribute certificate table, allowing limited tampering that older WinVerifyTrust implementations did not fully block. Revocation checks are soft by default, and revocation dates can leave an exploitation window open. Organizations should enforce publisher thumbprint allow-lists in WDAC or AppLocker and store signing keys exclusively in HSMs.
Critical Vulnerabilities in PaperCut NG and PaperCut MF Exploited in the Wild
PaperCut Software has disclosed two serious vulnerabilities in its printing management solutions PaperCut NG and PaperCut MF. The issues were detailed in an advisory published on August 27, 2026, followed by emergency patches. Exploitation has already been confirmed in customer environments. CVE-2026-81578 stems from improper access controls in the web management interface, allowing unauthenticated remote changes to system settings. CVE-2026-82078 involves insecure dynamic class loading in database connections, enabling arbitrary Java bytecode execution with server privileges when combined with the first flaw. CVSS scores are 9.4 (Critical) and 8.8 (High) respectively, and both vulnerabilities have been added to CISA’s Known Exploited Vulnerabilities Catalog.
Positive Technologies Develops Dynamic Crawler for Single-Page Applications in PT BlackBox Scanner
Positive Technologies engineers have detailed the development of a dynamic crawler for their PT BlackBox DAST scanner to handle modern single-page applications built with frameworks such as React and Vue. The crawler must discover attack surface elements that only appear after user interactions because static parsing of initial DOM fails on SPAs where navigation occurs without URL changes. Key challenges include identifying interactive elements whose handlers are attached via JavaScript, detecting state changes after clicks or inputs, and managing combinatorial explosion of states caused by independent UI toggles. The team models the application as a labeled transition system and defines state equivalence using sets of 64-bit fingerprints of interactive elements rather than raw HTML similarity or URL values. This equivalence relation satisfies reflexivity, determinism from external observations, cheap hash-based comparison, slower growth than action count, and preservation of enabled actions across equivalent states. The approach allows the crawler to visit representatives of equivalence classes instead of every reachable state, keeping scans finite and practical within action budgets of several thousand interactions.
Over 8,300 Gitea Servers Remain Exposed to Remote Code Execution via CVE-2026-60004
Thousands of publicly accessible Gitea instances were still unpatched against CVE-2026-60004 as of late August 2026, leaving them open to remote command execution. The critical vulnerability combines abuse of the diffpatch endpoint with the ability to install and trigger attacker-controlled Git hooks, allowing unauthenticated attackers to run commands on the server. Exploitation requires only write access to a repository, which is often trivial due to default open user registration in many deployments. The issue was fixed in Gitea 1.27.1 released on July 27, 2026, and CISA added the flaw to its Known Exploited Vulnerabilities catalog with a remediation deadline of August 28 for U.S. federal agencies. In observed incidents, attackers used the access to deploy cryptocurrency miners inside Docker containers. A related authentication bypass affecting the official Docker image, CVE-2026-20896, was also noted when reverse-proxy headers such as X-WEBAUTH-USER are enabled.