CISA Flags Two Actively Exploited Critical Flaws in Collabora Online and Arista VeloCloud

CISA’s addition means the agency considers both flaws actively exploited and important enough for defenders to prioritize. The vulnerabilities affect Collabora Online’s Built-in CODE Server when used with Nextcloud, and on-premise Arista VeloCloud Orchestrator. Both received critical severity ratings, making prompt patching especially important.

CVE-2026-110447 can enable operating system command injection through proxy.php when the local CODE document server is not running. CVE-2026-114625 is an SQL injection flaw in VeloCloud Orchestrator. It can expose privileged internal functionality to a remote attacker who meets the access requirements.

The catalog entry reflects confirmed exploitation, not merely theoretical risk. Attackers used the Nextcloud flaw to install web shells and search for sensitive data. Arista also confirmed active exploitation of its flaw. FCEB agencies are recommended to apply fixes by October 26, 2026.

A software vulnerability is a mistake or weakness in code, configuration, or design that lets an attacker bypass intended safeguards. The danger depends on what the flaw exposes, how reachable the software is, and what permissions the vulnerable process has. The two flaws in this article show different paths to impact.

Command injection happens when application input is passed into an operating-system command without being safely separated from the command itself. An attacker may then cause the server to execute additional commands. SQL injection occurs when input is inserted into a database query as executable SQL rather than treated as ordinary data. The attacker may access or alter database-controlled information.

Both attacks exploit poor separation between data and instructions. CVE-2026-110447 involves operating-system command injection in Collabora Online’s Built-in CODE Server. CVE-2026-114625 involves SQL injection in on-premise VeloCloud Orchestrator.

CVE-2026-110447 is an operating system command injection vulnerability in Collabora Online’s Built-in CODE Server, also called richdocumentscode. It affects deployments using the NextCloud platform when the CODE local document server is not running. In that condition, the vulnerable proxy.php path can handle attacker-controlled input in an unsafe way.

The core mechanism is a failure to keep data separate from commands. Instead of treating a request as ordinary document-service information, the server can interpret crafted input as instructions for the underlying operating system. That creates a route to remote code execution. The attacker does not need to be physically present on the server.

Reports described attackers using the flaw to backdoor Nextcloud servers with web shells. They then conducted reconnaissance and searched for credential stores, password-manager artifacts, and cryptocurrency wallets. The flaw was fixed in September 2026, in version 26.4.303, but exposed systems remain at risk until updated.

This is a high-priority security event because both vulnerabilities are critical and already being exploited. Their CVSS scores are 9.2 and 9.9, placing them near the top of the severity scale. A score alone does not prove an attack is happening, but these scores are reinforced by reports of exploitation in the wild.

The impact is especially clear for the Collabora flaw. Attackers used it to install web shells on Nextcloud servers, perform reconnaissance, and search for credential stores, password-manager artifacts, and cryptocurrency wallets. The VeloCloud flaw could provide access to privileged internal functionality after successful exploitation.

The broader pattern is also alarming. CVE-2026-114625 is the third VeloCloud vulnerability weaponized in the wild since July 2026. The other two, CVE-2026-16812 and CVE-2026-93952, each had a CVSS score of 10.0. Organizations should treat patching as urgent, not routine.

CVE-2026-114625 was not described as exploitable by any unauthenticated internet user. The attacker needed network access to the VeloCloud Orchestrator web interface and a valid authenticated session on the VCO portal. Those requirements narrow the entry path, but they do not remove the danger.

The minimum required role was Enterprise Read Only. That detail matters because a low-privilege account could still satisfy the vulnerability’s access condition. Once the SQL injection succeeded, the flaw could let a remote attacker access privileged internal functionality. The article does not state exactly what attackers did after escalation.

Arista has acknowledged that the vulnerability is known to be actively exploited. It has not identified a threat actor, explained the exploitation steps, or disclosed how many organizations were affected. The vulnerability was fixed in versions 5.2.3.18, 6.1.3.10, and 6.4.2.12, so exposed operators should update and review access.

Leaving either flaw unpatched gives attackers more time to exploit a weakness that is already being used. A compromised server or orchestrator could become a foothold inside an organization’s environment. The article specifically links the Nextcloud flaw to remote code execution and backdooring, while the VeloCloud flaw could expose privileged internal functionality.

In observed attacks, threat actors installed a web shell on a Nextcloud server. A web shell can provide continuing access through the compromised web application. They also conducted reconnaissance and searched for credential stores, password-manager artifacts, and cryptocurrency wallets. Those targets could reveal secrets or valuable assets stored on or reachable from the server.

The article does not disclose the full post-exploitation impact for VeloCloud or the number of affected organizations. Arista shared two Japan-geolocated IP addresses associated with the activity. The fixes are available, and FCEB agencies are recommended to apply them by October 26, 2026.

Web applications often need to send information to operating-system tools or databases. Safely designed software treats user input as data, not as instructions. It validates expected values, limits formats and permissions, and uses separate interfaces that preserve the boundary between input and executable operations.

For databases, parameterized queries keep supplied values separate from SQL syntax. For operating-system tasks, applications should avoid shell interpretation where possible and pass fixed arguments through controlled APIs. They should also use allowlists, least privilege, and careful error handling. These controls reduce the chance that special characters or crafted text changes what the system executes.

The fundamental failure is mixing untrusted input with executable code. In the Collabora case, that weakness enabled operating-system command injection through proxy.php. In the VeloCloud case, it enabled SQL injection. The article identifies the vulnerabilities and impacts, but does not provide their detailed code-level causes.