Skip to content
BlogSoftware

Software4 min read

Your own file server is safer than Google Drive. Unless nobody updates it

Hackers are taking over company Nextcloud servers through the built-in Collabora app. Why so many missed it, and what to check today.

Amine KHDev, Tradix Technology
00:00-05:23

What happened

Nextcloud is the most popular way for a company to run its own "Google Drive": shared folders, calendars, file links for clients, all on a server you control. Many installations add Collabora, so people can open and edit Word and Excel files in the browser. The simplest way to get it is an app called Built-in CODE Server, which runs the office engine on the same machine.
That app had a serious mistake. A script that should only pass messages along was building a server command out of text sent from the internet. With the right request, a stranger could make the server run their own commands, without an account. The flaw is rated 9.2 out of 10. (For your technical team: CVE-2026-110447.)
Administrators started seeing attacks around September 10. The attackers planted small hidden programs called "web shells", which give them a permanent back door, then went looking for password files and cryptocurrency wallets. On October 23, CISA added the flaw to its list of vulnerabilities known to be exploited.

Why so many people missed it

This is the part I find most instructive. Two details made this flaw easy to overlook, even for careful administrators.
It only opens when the office app is down. The dangerous code runs when the built-in office server is not running: after a restart, after an update, after a crash. A server that seems to work normally can be exposed for hours without anyone noticing anything.
"Disable" doesn't mean "safe". The natural reflex is to switch the app off in the Nextcloud admin panel. That doesn't help: the faulty script stays on the disk and can still be reached. Only the update, or removing the app completely, closes it.
The fix may need a bigger move. The fixed versions require Nextcloud 30 or newer. If your server is on Nextcloud 29 or older, which no longer receive updates, you can't simply click "update" on the app. You first have to upgrade Nextcloud itself. That's how a ten-minute fix turns into a project, and projects get postponed.

The real story: owning your data means owning the updates

In Algeria, many companies chose Nextcloud for good reasons: keeping client files in the country, respecting the personal-data law, not depending on a foreign service that can change its prices or its rules overnight. I think it's the right choice, and we recommend it ourselves.
But when you move your files off Google or Microsoft, you also take over a job they were doing for you: watching for flaws and updating within days. Very often, the server was installed once by a provider or a motivated employee, it works, and nobody has been named to look after it since. That's exactly the profile this kind of attack is waiting for.
Self-hosting is not the problem. Self-hosting without someone responsible for updates is.

Are you affected?

You are probably affected if all three are true:
  1. You run Nextcloud on your own server or a rented one
  2. Users can open documents in the browser with Collabora (or "Nextcloud Office")
  3. It works through the Built-in CODE Server app, older than version 26.4.303
According to the reports, a separate Collabora Online server, Docker or package installations of Collabora, and Nextcloud All-in-One are not affected. If you don't know which one you have, ask whoever installed it today.

What to do today

1. Check the app version. In Nextcloud, go to Apps, then "Built-in CODE Server". It must be 26.4.303 or newer.
2. Update, or remove the app. If you can't update today, uninstall it completely. People will lose in-browser editing for a while, which is better than losing the server.
3. On Nextcloud 29 or older? Plan the upgrade this week. These versions no longer get security fixes at all, not only for this flaw.
4. Look for signs of intrusion: PHP files you don't recognise in the Nextcloud folder, new admin accounts, unusual outgoing connections, or a server that's slower than usual.
5. If you find a back door, rebuild instead of cleaning. Install a fresh server, restore your files from a backup, and change every password that was stored on or used with the old one.

The lesson for the next one

This won't be the last flaw of its kind. What matters isn't whether your software is perfect, because none is. What matters is whether someone in your company knows they are responsible for updates, and how many days they need to react when an alert like this one comes out.
Share

Written by

Amine KH

Keep reading