# CVE-2026-110447: Collabora Online – Built-in CODE Server OS Command Injection

> Remote attackers can execute arbitrary OS commands via proxy.php when the CODE server is not running, affecting Nextcloud deployments using this specific built-in server.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Yes, since 23 Oct 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-f97p-r72q-64h2

## What is CVE-2026-110447?

CVE-2026-110447 is a critical command injection vulnerability in Collabora Online - Built-in CODE Server, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Collabora Online Built-in CODE Server before 26.4.303 (richdocumentscode), a Nextcloud app, allows remote code execution, as exploited in the wild in September and October 2026, a different vulnerability than CVE-2025-66208. This is an OS command injection in proxy.php when the CODE server isn't running (e.g., the product was recently restarted). The vulnerability is not present in standalone Collabora Online servers; only this deployment with CODE Server is affected.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-110447?

It affects 1 product.


Products: Collabora Online.

## How do I fix CVE-2026-110447?

No fix has been published for CVE-2026-110447 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 26 Oct 2026.

## Is CVE-2026-110447 being exploited?

Yes. Attackers have exploited CVE-2026-110447 in the wild since at least 23 Oct 2026.

Public exploit code:

- https://github.com/CyRouteWolf/cve-2026-110447-poc (github_poc): https://github.com/CyRouteWolf/cve-2026-110447-poc
- https://github.com/adriyansyah-mf/cve-2026-110447 (github_poc): https://github.com/adriyansyah-mf/cve-2026-110447
- Collabora Built-in CODE Server < 26.4.303 - OS Command Injection (nuclei): http/cves/2026/CVE-2026-110447.yaml

## Other vulnerabilities in Collabora Online - Built-in CODE Server

- [CVE-2021-32744](https://insights.sbomify.com/CVE-2021-32744/): Unauthenticated attacker could gain access to currently open files (critical 9.8)
- [CVE-2021-43817](https://insights.sbomify.com/CVE-2021-43817/): Reflected Cross-Site-Scripting vulnerability in Collabora Online (high 8.2)
- [CVE-2021-32745](https://insights.sbomify.com/CVE-2021-32745/): Reflected Cross-Site-Scripting vulnerability (high 7.3)
- [CVE-2025-66208](https://insights.sbomify.com/CVE-2025-66208/): Configuration-Dependent RCE (OS Command Injection) in richdocumentscode proxy (high 7.2)
- [CVE-2024-45045](https://insights.sbomify.com/CVE-2024-45045/): JavaScript Injection via url encoded values in links in Collabora Office Android (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110447 and fix it if it is affected.

What it is: CVE-2026-110447 is a critical command injection vulnerability in Collabora Online - Built-in CODE Server, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-110447 in the wild since at least 23 Oct 2026.

Affected product: Collabora Online - Built-in CODE Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110447/ (Markdown: https://insights.sbomify.com/CVE-2026-110447/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110447
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110447
- OSV: https://osv.dev/vulnerability/CVE-2026-110447

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110447/
Summaries are generated and may contain mistakes; the official description above is the record.