As reported by CISA on October 23, 2026, the agency has added CVE-2026-110447 — an operating system command injection vulnerability in Collabora Online's Built-in CODE Server — to its Known Exploited Vulnerabilities (KEV) Catalog. The inclusion confirms active exploitation in the wild, elevating this from a theoretical patching priority to an immediate defensive imperative.
Collabora Online is widely deployed as the document editing backbone for Nextcloud, ownCloud, and self-hosted file-sharing environments. Its Built-in CODE (Collabora Online Development Edition) Server processes office documents server-side — a functionality that inherently involves complex file parsing and system-level operations. An OS command injection flaw in this component means an attacker can escape the application context and execute arbitrary commands on the host operating system, effectively achieving full server compromise without requiring authentication in many deployment configurations.
Why This Vulnerability Demands Urgent Attention
OS command injection vulnerabilities are among the highest-impact flaw classes because they bypass application-layer controls entirely. In Collabora's architecture, the server component runs as a service with broad file-system access to process documents — meaning post-exploitation access extends well beyond the application to any data the server can reach, including uploaded documents, configuration files, and potentially adjacent network resources.
The attack surface is significant: Collabora Online instances are frequently deployed in enterprise and educational environments where they are internet-exposed to support remote document collaboration. Organizations running Nextcloud or ownCloud with Collabora integration should consider themselves in the primary risk cohort.
Vulnerability Details
| CVE ID | CVE-2026-110447 |
| Vendor / Product | Collabora Online – Built-in CODE Server |
| Vulnerability Type | OS Command Injection |
| Severity | Critical (OS command injection with active exploitation, KEV-listed) |
| Exploitation Status | Confirmed active exploitation in the wild |
| Primary Risk | Unauthenticated remote code execution leading to full server compromise |
| Most Affected | Internet-exposed Collabora Online / CODE Server deployments, Nextcloud/ownCloud integrations |
CISA's KEV Catalog inclusion is not a advisory — it is a confirmation that threat actors are already using this vulnerability against real targets. The window between disclosure and exploitation has effectively closed.
Who Is at Risk
Shield53 Recommendations: Immediate Actions
- Patch immediately. Check the Collabora product advisory for the fixed version and upgrade your CODE Server instance without delay. If a patch is not yet available for your deployment method, contact Collabora support directly.
- Restrict internet exposure. If Collabora does not need to be publicly accessible, move it behind a VPN or zero-trust access layer immediately. If it must remain exposed, enforce IP allowlisting at the reverse proxy level.
- Review server logs for indicators of compromise. Look for unexpected process executions originating from the Collabora service account, unusual outbound network connections, and modifications to system files outside expected document storage paths. Given confirmed active exploitation, treat the system as potentially compromised until verified clean.
- Isolate the Collabora container/service. If running in a containerized environment, verify that the CODE Server container has restricted capabilities, read-only file systems where possible, and limited network egress. Network segmentation between the document server and core infrastructure limits lateral movement if exploitation occurred.
- Verify document processing isolation. Ensure the Collabora service runs under a dedicated, least-privilege user account and that SELinux or AppArmor profiles are enforced — these controls can limit the blast radius of command injection even when the application vulnerability is triggered.
- Subscribe to CISA KEV updates. If your vulnerability management program does not automatically ingest the KEV Catalog feed, integrate it now. KEV additions should trigger expedited triage workflows, not routine patching queues.
The broader implication here is structural: document processing servers remain a persistent blind spot in many organizations' vulnerability programs. They handle untrusted input (uploaded files), execute complex parsing logic, and are frequently deployed with more permissive configurations than other application servers. Until Collabora releases full technical details, defenders should assume the worst — unauthenticated RCE on any unpatched, internet-facing instance — and act accordingly.
