The short version
- The flaw. Collabora Online - Built-in CODE Server (package richdocumentscode) is an optional Nextcloud app that runs a local Collabora document server. In versions before 26.4.303 its proxy.php script passed text from a request path into a shell command, letting an unauthenticated attacker run commands as the web server user. It only worked while the local document server was stopped.
- The exploitation. Administrators reported web shells named shx*.php planted in the app's folder from 10 September onwards, and searches for password databases, password manager files and cryptocurrency wallets. No report shows the attacker reaching root.
- The disclosure gap. The fix shipped on 11 September; the advisory and CVE appeared on 14 October. Nextcloud told BleepingComputer it delayed to give users time to update and said it saw no widespread exploitation. Collabora attributed the delay mainly to GitHub CVE-processing backlogs.
- Who is exposed. Only the built-in app is affected. Collabora says standalone Collabora Online servers, Docker and package installations and Nextcloud All-in-One deployments are not. Nextcloud 29 and older are end of life and the app store still serves them an affected version.
Timeline
| Date | Event |
|---|---|
| 9 September | Collabora commits the code change that closes the flaw in proxy.php. |
| 10 September | First logged attack: a request to proxy.php?status carrying a shell command in its path, at 19:51 (UTC+2) from 139.28[.]18[.]122. |
| 11 September | Version 26.4.303, the fixed release, is published. |
| 14 September | A second IP address, 89.38[.]98[.]50, sends a similar attempt against a server already updated to 26.4.303; no new shell file appears. |
| 24 September | Version 26.4.402 rewrites the start command, but administrators report start-up and document-opening failures on some setups and return to 26.4.303. |
| 3 October | A warning is posted on the Nextcloud community forum telling administrators to update. |
| 14 October | Collabora publishes its advisory and CVE-2026-110447 is issued. |
| 15 October | Collabora publishes a blog post on the activity and Nextcloud answers questions about its response. |
How the flaw worked and how it was fixed
The app downloads a copy of Collabora Online Development Edition and runs it on the Nextcloud server, so Nextcloud Office can edit documents without a separate Collabora host. Its store listing describes it as intended for local testing and non-production use, and for personal use or small teams. The vulnerable code is a plain PHP file, proxy.php, that the web server runs directly and that loads none of Nextcloud's own code.
When a request arrived and nothing was listening locally, proxy.php started the bundled server. In versions up to 26.4.302 it placed request text, including the path, inside a double-quoted bash command, where the shell still runs anything written as $(...). Because the command is only built when the server needs starting, an attack works only during a restart, an upgrade or after a crash. No authentication or user interaction is needed.
Collabora fixed the flaw in 26.4.303 and says disabling the app is not enough: "It is not sufficient to disable the app to avoid the problem; it must be upgraded to >= 26.4.303 or removed." The fixed versions require Nextcloud 30 or later. Version 26.4.402, released on 24 September, rewrote the start command to pass each option separately, but some administrators found it would not start or open documents and reverted; no newer release had appeared as of 14 October.
What the attackers did
The first report came from an administrator running several Nextcloud servers, all on 26.4.302, whose access logs show requests on 10 and 11 September from one IP address aimed at proxy.php?status with a command hidden in the path. The command decoded a one-line PHP web shell into the app's folder and tried to send the server's system information to a public webhook service.
On one server the attacker used the shell to search for credential stores and cryptocurrency wallets, including KeePass databases, wallet.dat and keystore.json files and files named after password managers and coin wallets. The reviewed requests contained no commands that archived, uploaded or copied files out, but the administrator wrote that anything the web server account could read should be treated as potentially exposed. None of the reports show root access.
Two other administrators found the same activity, one through Nextcloud's integrity check flagging a new PHP file and one through emails about failed sudo attempts on the server. BleepingComputer says some users reported that ransomware operators were exploiting the flaw, but the publication could not independently confirm this, and no source links the two claims.
Scope and the disclosure gap
According to Collabora, only the built-in app is affected; standalone Collabora Online servers, Docker and RPM/DEB installations and Nextcloud All-in-One deployments are not. An installation that uses only the Nextcloud Office app with a separate Collabora server is also unaffected. Nextcloud 29 and older cannot install the fixed version, are end of life and are still served an affected version by the app store.
Nextcloud told BleepingComputer that Collabora reported the vulnerability in mid-September and that an update became available through the app store, and said the delay gave users time to update. Collabora's blog post attributed the delay primarily to GitHub CVE-processing backlogs, which it said were strained by growing volumes of AI-driven security reports.
BleepingComputer cites a study by Second Security finding the median interval between a public open-source fix and CVE publication was 39 days in August, up from 5.1 days in January, and that exploit code often appeared within hours of a fix. The publication says the absence of a CVE ID made it harder for administrators to identify the issue and defend against it.
What is not known yet
- Who carried out the attacks, and whether the two IP addresses used belong to one operator.
- How many Nextcloud servers were compromised in total.
- Whether any credential stores or cryptocurrency wallets were actually read or taken, beyond the searches seen in the logs.
- Whether ransomware operators were involved at all; BleepingComputer could not confirm the reports.
- Whether a release after 26.4.303 that starts reliably on affected setups has shipped.
What to do
If you run Nextcloud with the Built-in CODE Server
- Update richdocumentscode to 26.4.303 or later, or remove the app; disabling it in Nextcloud does not close the flaw.
- On Nextcloud 29 or older, which cannot install 26.4.303, upgrade Nextcloud or remove the app.
- Look for files named shx*.php, starting in apps/richdocumentscode, and delete any you find.
- Check access logs back to at least 10 September for proxy.php?status requests whose path contains %2e%2e, $( or ${IFS}, and for sudo attempts by the web server account; treat anything that account could read as exposed and rotate those credentials.
If you run a separate Collabora server
- Confirm you use only the Nextcloud Office app (richdocuments) with a standalone Collabora Online server, in Docker, from a Linux package or at a hosting provider, rather than the built-in app; Collabora says those setups are not affected.
For everyone else
- Treat a public fix in an internet-facing component as a signal to patch immediately, even before a CVE ID or advisory exists, and watch logs for exploitation in the gap.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.