Critical Vulnerabilities Detected in Ruby on Rails and Arista VeloCloud SD-WAN Orchestrator
On August 3, 2026, CERT-FR released bulletin CERTFR-2026-ACT-033, highlighting two critical vulnerabilities present in significantly different components: the Ruby on Rails library, which serves as the backbone for thousands of web applications, and Arista’s VeloCloud SD-WAN orchestrator, which manages networks for numerous enterprises. The first, identified as CVE-2026-66066, transforms a simple image upload into arbitrary file reading and eventually results in code execution. The second vulnerability, CVE-2026-16812, received the highest severity rating of 10 out of 10 and is reportedly being actively exploited against exposed orchestrators without requiring any user credentials.
On July 29, 2026, the Ruby on Rails project released a patch addressing CVE-2026-66066, a flaw within the Active Storage component responsible for handling user-uploaded images. Just two days earlier, on July 27, Arista Networks had issued a fix for CVE-2026-16812 affecting the VeloCloud Orchestrator, the software that centralizes configuration for SD-WAN-connected sites. CERT-FR connected the two vulnerabilities on August 3, noting that both are considered among the most serious on their scale, especially given their inherent exposure.
The flaw in Active Storage arises when an application utilizes libvips to generate image variations, a setting that has been the default since Rails 7.0. An unauthenticated attacker can create a file that libvips recognizes as a MATLAB-format image, but which the libmatio library identifies as an HDF5 version 7.3 container. This HDF5 format includes a feature called external file listing, intended for referencing data stored elsewhere. The compromised file manipulates this to point to a path chosen by the attacker, resulting in the content being read as image pixels and returned in the generated variant.
Forging a False Key to Execute Code on the Server
Researchers at Rapid7 found that an attacker who retrieves the application’s secret_key_base signing key through this method can forge a variant in the ImageProcessing library format, leading to remote code execution on the server. This complete exploitation chain was reconstructed by the publisher on July 31, following several researchers’ release of a demonstration code that they obtained through reverse engineering weeks prior to the full disclosure scheduled for August 28. It’s worth noting that this file reading does not require pre-existing secrets—simply delivering one suffices. As of August 3, Rapid7 has reported no confirmed exploitation in production environments; however, the public availability of demonstration code reduces this grace period to a matter of days.
The fix for this exploitation chain applies to released versions 7.2.3.2, 8.0.5.1, and 8.1.3.1 of Active Storage. Rails branches 7.0 and 7.1, which are no longer under security support, will not receive this update and must be upgraded to a fixed version. Additionally, Rails requires a minimum libvips library version of 8.13; otherwise, the application will refuse to start. It is also recommended to rotate the secret_key_base and the credentials it protects. Until an update can be applied, the variable VIPS_BLOCK_UNTRUSTED mitigates risky operations in recent versions of libvips.
An Internal Feature That Should Never Have Been Exposed
The CVE-2026-16812 vulnerability in the Arista VeloCloud Orchestrator allows an attacker to access an internal feature reserved for the software’s operational needs without requiring any credentials. The resulting command injection provides full control over the host and, by extension, the VeloCloud Edge peripheral devices managed by the orchestrator at connected sites. Scoring a 10 out of 10 on both the CVSS 3.1 and 4.0 scales, this vulnerability was discovered by an external party who noticed active exploitation prior to the patch’s release, making it a zero-day vulnerability.
The orchestrator is exposed by default on its web interface, and no configuration eliminates this exposure. Only restricting access to trusted management networks can reduce risk before a fix is implemented. Arista has addressed the vulnerability in versions 5.2.3.14, 6.1.3.4, and 6.4.2.4 of the orchestrator, as well as in the versions hosted by the publisher, which were added to the affected platforms list on August 3. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has listed this vulnerability in its catalog of actively exploited vulnerabilities and mandated a remediation deadline by July 30 for federal agencies, just three days after its addition, as required by federal directive BOD 22-01.
Arista has shared three IP addresses identified in the attacks and recommended reviewing web access logs for unusual URL components or request spikes, followed by scanning system logs for unexpected commands or database exports. In the event of confirmed compromise, the publisher advises credential rotation and inspection of the VeloCloud Edge devices managed by the affected orchestrator.
Two Urgency Timelines, One Discipline
In the case of VeloCloud Orchestrator, active exploitation preceded the fix, providing no window for teams to prepare and necessitating immediate investigation upon patch application. On the Ruby on Rails front, Rapid7 did not confirm any exploitation to date. Thus, the two vulnerabilities outlined in the CERT-FR bulletin call for different levels of urgency. However, the public demonstration code and an already reconstructed exploitation chain shorten the respite to mere days. Severity scores alone do not adequately differentiate between these two situations. This concurrent vulnerability highlights a continuing trend where an exposed application gateway has previously allowed for code execution through a comparable mechanism, manipulating data input beyond its intended function to execute commands.
Ultimately, only tracking the exploitation status as published by CERT-FR, CISA, and other publishers can appropriately prioritize this week’s patches rather than relying solely on CVSS scores. The upcoming Cyber Resilience Act, mandating notifications of exploited vulnerabilities within 24 hours, goes into effect on September 11, 2026, and will promote early reporting habits among manufacturers selling in Europe, aiming to close the gap between the discovery of vulnerabilities and the publication of active exploitation.



