Check a site
Check a website Service status Outages Blog
All tools
Check a websiteBrowse all tools
A terminal running Nextcloud occ commands that show richdocumentscode going from 26.4.302, marked vulnerable, to 26.4.502, marked fixed

WarningAlerts

Nextcloud’s Built-in CODE Server is being exploited: update or remove it

Posted Jimel S.4 min read

A command injection bug in the Collabora Online Built-in CODE Server app for Nextcloud was exploited in September and October 2026. Disabling the app doesn’t protect you. Update it to 26.4.303 or later, or remove it, then check the server for web shells.

Illustration: UtiBox

Warning

Ongoing

Nextcloud Built-in CODE Server flaw CVE-2026-110447 is being exploited. Update richdocumentscode to 26.4.303 or later, or remove it.

Started
Ends
Not known yet

What happened

Nextcloud can edit office documents through Collabora Online. One way to set that up is the Built-in CODE Server app, richdocumentscode, which runs a copy of Collabora inside your Nextcloud server instead of a separate one.

That app had a bug in its proxy.php file. According to the CVE record, versions before 26.4.303 allow remote code execution “as exploited in the wild in September and October 2026”. Collabora’s own advisory, published on 14 October 2026, says “a request can cause an operating system command to run as the web server user”. It rates the bug Critical, with a CVSS 4.0 score of 9.2.

On 23 October 2026 CISA added CVE-2026-110447 to its Known Exploited Vulnerabilities (KEV) catalog, with a deadline of 26 October for US federal agencies.

The catch: it bites after a restart

The attack only works while the built-in CODE server isn’t running. The advisory gives examples: a container restart, an upgrade, or a crash. A server that has been up for weeks can become exploitable the moment it reboots.

That’s also why turning the app off doesn’t help. The advisory is explicit: “It is not sufficient to disable the app to avoid the problem, it must be upgraded to >= 26.4.303 or removed.”

Who is affected

Set-upAffected?
Nextcloud with the richdocumentscode app before 26.4.303, enabled or disabledYes
Nextcloud using a separate, standalone Collabora Online serverNo (the advisory says standalone servers aren’t affected)
Nextcloud 29 or older with richdocumentscodeYes, and recent app versions need Nextcloud 30 or later, so upgrade Nextcloud or remove the app

The fixed release, 26.4.303, has been on GitHub since 11 September 2026. Collabora has released 26.4.402 and 26.4.502 since then. A server that updates its apps regularly may already be fixed, but check rather than assume.

How to check and update

Run these as the web server user from your Nextcloud folder. The commands come from Nextcloud’s administration manual. Adjust www-data and the path to match your system.

# Which version is installed?
sudo -E -u www-data php occ app:list | grep richdocumentscode

# Update it ...
sudo -E -u www-data php occ app:update richdocumentscode

# ... or, if you don't use it, remove it completely
sudo -E -u www-data php occ app:remove richdocumentscode

In the web interface, the same app appears under Apps as “Collabora Online - Built-in CODE Server”.

Look for signs of compromise

The attacker’s commands run as the web server user, which can read your Nextcloud configuration (database password included) and write files into the Nextcloud folder. If the app was installed before you updated it, especially across a reboot or upgrade during September or October, work through these checks (our suggestions):

Integrity checks. Nextcloud can compare apps and core files against their signatures. No output means the files match. Unexpected extra .php files are a strong sign of a web shell.

sudo -E -u www-data php occ integrity:check-app --all
sudo -E -u www-data php occ integrity:check-core

Access logs. Look for requests to richdocumentscode/proxy.php that contain shell syntax, such as $( or its URL-encoded form %24%28. Use your Apache log path if you run Apache.

sudo zgrep -h 'richdocumentscode/proxy.php' /var/log/nginx/access.log* | grep -E '\$\(|%24%28'

Everything else. Look for recently changed PHP files in the Nextcloud folder that you can’t explain, and for new cron jobs or processes owned by the web server user.

If you find anything, treat the server as compromised. Back up your data, rebuild Nextcloud from a clean install, and restore only data, not code. Then rotate everything the web server could read: the database password, mail and external storage credentials, and API tokens for other services. Ask users to change their passwords and app passwords. Our guide to rotating leaked secrets covers the order to do it in.

Longer term

The Built-in CODE Server is the quick option. For anything beyond a small or test install, running Collabora as its own service (a container or a distribution package) keeps Nextcloud’s PHP process from starting and managing another server. That is the set-up this bug didn’t affect.

Sources

Related

More from Alerts

Most read

Latest

Most read

  1. 01November Patch Tuesday lands on the 10th: what October’s record release tells us19
  2. 02Introducing UtiBox: the Web’s Utility Box2
  3. 03Ivanti Connect Secure zero-days gave attackers root on VPN gateways1
  4. 04“Black October”: attackers raid secrets at cloud and AI developer platforms1

Embed this post

Paste this code into your page. It shows the post as a card that links back here. In WordPress you can also paste the post’s address on a line of its own.

Cookies on UtiBox

UtiBox is free because of ads. Google and its partners use cookies to show, limit and measure ads, Google Analytics, Ahrefs Web Analytics and Microsoft Clarity show us how the site is used, and we use a few essential cookies to run the site.