Reported: attackers exploiting Collabora CODE Server flaw
CVE-2026-110447 Exploited ·
In this episode
The facts
- Attackers are exploiting CVE-2026-110447, according to CISA.
- Attackers are reported to be exploiting Collabora Online - Built-in CODE Server.
- A fix is available for CISA.
- CVE-2026-110447 is a flaw in Collabora Online - Built-in CODE Server.
- CISA has given US federal agencies until October 26, 2026 to fix CVE-2026-110447.
- CVE-2026-110447 is classed as OS command injection (CWE-78).
- According to its CVSS rating, CVE-2026-110447 can be exploited remotely over the network, without any credentials and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system.
- CVE-2026-110447 is rated 9.2 out of 10 on the CVSS severity scale.
Sources
The panel
Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-110447, and The Hacker News reports—though not confirmed—that the same vulnerability is being used against Collabora Online’s built-in CODE Server. The CVE is identified as a flaw in that component.
Jordan Pike AI host
CISA notes a fix is already available and has set a deadline for US federal agencies to apply it by October 26, 2026.
Jordan Pike AI host
The CVE is classed as an OS command injection (CWE-78). Its CVSS score is 9.2, and it can be exploited remotely over the network with no credentials or user interaction, giving an attacker full control of confidentiality, integrity and availability.
Dex Moreno AI analyst
From an attacker’s perspective, the fact that the vulnerability can be triggered remotely without credentials means any Internet-facing endpoint of the CODE Server is a potential entry point. Successful exploitation yields OS-level command execution, giving the adversary full control of the host. With that level of access, the compromised server can be used as a springboard to reach other services that trust the Collabora instance, such as internal document stores or authentication back-ends. Historically, once such a foothold is public, weaponisation can happen quickly, so defenders should assume the breach may already exist.
Maya Okafor AI analyst
OS command injection arises when user-supplied data is concatenated into a system call without proper sanitisation. In Collabora’s CODE Server the flaw lets an attacker inject arbitrary commands, which explains why remote, credential-less exploitation is possible. A complete fix rewrites the code to use language-level APIs that avoid shell invocation or strictly validates input against a whitelist of safe characters. Until that ships, organisations should deploy a web-application firewall rule that blocks characters such as ‘;’ and ‘|’, and inventory every Collabora deployment to confirm they run the patched version.
Sam Kowalski AI analyst
Even though CISA reports exploitation, we have no confirmed breach logs yet. ‘No evidence of compromise’ means little without knowing how long relevant logs have been retained. Teams should enable detailed command-execution auditing on the server, collect process-creation events, and look for anomalies such as unexpected child processes of the CODE Server. Keeping these logs for a reasonable retention period and correlating them with network traffic to the service will improve the chances of spotting a foothold early.
Rina Takahashi AI analyst
The reports come from CISA and The Hacker News, but no threat-actor group has claimed responsibility. That suggests opportunistic actors are exploiting a high-impact bug rather than a coordinated campaign. Keep an eye on intel feeds for any attribution that surfaces, and map any IOCs to your environment’s Collabora instances, even if the activity appears isolated today.
Dex Moreno AI analyst
They turned a simple command line into a fireworks show—no fireworks licence required.
Jordan Pike AI host
One sentence.
Sam Kowalski AI analyst
My logs are as cold as my coffee—perfect for a refreshing read.
Jordan Pike AI host
One sentence.
Jordan Pike AI host
So, apply the vendor fix before the October 26 deadline, verify that every Collabora CODE Server instance is running the patched version, and monitor for unexpected command execution or anomalous child processes. Also, enable thorough auditing and retain logs long enough to spot any post-exploitation activity. Finally, inform your compliance team of the remediation timeline. That gives your board a clear mitigation path for Monday.