Collabora’s Nextcloud CODE server flaw was exploited for five weeks before it had a CVE
CVE-2026-110447 was under attack from 10 September, patched on 11 September, given a CVE on 14 October and added to KEV on 23 October. Defenders who wait for identifiers missed the whole window.
A command injection flaw in Nextcloud’s optional Collabora Online Built-in CODE Server app was being exploited on 10 September 2026. It received a CVE on 14 October and a CISA Known Exploited Vulnerabilities (KEV) entry on 23 October. For about five weeks, the only public signals were a GitHub issue, a forum thread and an app update with no advisory attached [3][4][1][8]. Any patch programme that waits for a CVE identifier missed the whole of that window.
What happened
CVE-2026-110447 affects the richdocumentscode app, which bundles a Collabora Online Development Edition (CODE) server inside a Nextcloud instance. Versions before 26.4.303 are affected. Collabora’s advisory classes it as CWE-78 OS command injection in the app’s PHP proxy. It is rated critical, CVSS v4 9.2 [1]. An unauthenticated request can run an operating system command as the web server user. This only works while the bundled CODE server is not running, for example after a container restart, an upgrade or a crash [1]. Standalone Collabora Online servers are not affected. Collabora says Docker images, RPM/DEB packages and Nextcloud All-in-One images are also unaffected, and that none of its Collabora Online customers were [2].
The first public evidence came from administrators, not the vendor. In issue #354 on the richdocumentscode repository, an operator of several Nextcloud servers reported intrusions on version 26.4.302. Attackers had planted PHP web shells and run commands through them. The earliest logged request was dated 10 September [3]. On one system, the web shell was used to search for credential stores and cryptocurrency-related files. The reporter found no explicit evidence of exfiltration but advised treating data readable by the web server account as exposed [3]. At least three separate operators reported compromise in the thread [3]. On 23 September, another administrator posted log entries from 18 September. They showed the web server user trying to read Nextcloud’s LDAP configuration from the app directory [5].
BleepingComputer reports that the fix was committed on 9 September and that version 26.4.303 shipped on 11 September [10]. A community warning on the Nextcloud forum followed on 3 October [4]. Collabora published its advisory on 14 October [1]. CISA added the flaw to KEV on 23 October, with a federal remediation date of 26 October [8][9]. NVD added a CVSS v3.1 score of 9.8 and CPE data on 26 October [7]. The scores differ: the CNA score is v4 9.2 and NVD’s is v3.1 9.8 [7]. iThome, reporting on 19 October, noted that attacks had by then been running for at least a month [14].
Why the advisory was late
The vendors explain the gap differently. Collabora puts it mainly down to the CVE process. It says the time to get a CVE filed and published through GitHub went from around a day to many weeks this year. It is applying to become a CVE Numbering Authority so it can publish directly [2]. It also says AI-driven security audit reports of mixed quality have added heavy load. By its own account, it has processed about ten years’ worth of security reports so far this year [2]. Nextcloud gave BleepingComputer a different reason. It said the delay gave users time to update, and that it had not seen widespread exploitation [10]. Those two accounts are not reconciled in any public material we found.
The GitHub backlog Collabora describes is documented. GitHub’s Advisory Database team said its CNA received almost 4,000 CVE requests in May 2026, nearly ten times the figure a year earlier. Private vulnerability reports rose from about 550 a week in January to more than 3,000 a week for most of May [11]. Since mid-April, publication has stretched to about a week, and then to several weeks for a meaningful share of advisories. GitHub states that longer publication times can extend exposure windows [11]. The CVE record that was published lists MITRE as the assigner, according to OpenCVE’s copy of it [7]. The global GitHub advisory entry for this CVE is still marked unreviewed. It lists no package and gives affected and patched versions as unknown [6]. Tools that match only on that database’s package data would not flag it.
A second hole in the same proxy
This is not the app’s first proxy flaw. In December 2025, Collabora published CVE-2025-66208, a configuration-dependent command injection in the same richdocumentscode proxy. It was fixed in 25.04.702 [12][13]. Collabora rated that issue moderate, and its CVSS v4 score is 7.2. INCIBE-CERT lists a CVSS v3.1 score of 9.8 [12][13]. The new advisory states that the earlier fix does not prevent CVE-2026-110447 [1]. A patched instance from December was still exposed in September.
What it means
Three points matter for defenders. First, the fix itself was the disclosure. Attacks started before 26.4.303 shipped and went on after it, while no CVE existed to drive scanners, SLAs or KEV-based prioritisation [3][10]. Second, patching does not clean up. One operator reported further web shell creation attempts after upgrading. These failed, and Nextcloud’s integrity check flagged a newly created PHP file [3]. Collabora’s guidance is to upgrade or remove the app. Disabling it is explicitly not enough [1][2]. Third, the exposure condition is operationally common. Restarts, upgrades and crashes all open the window [1].
There is also a version constraint. A forum contributor noted on 26 October that the fixed release needs Nextcloud 30 or later [4]. The advisory tells users on end-of-life Nextcloud 29 and earlier to upgrade Nextcloud or remove the app [1]. Collabora describes the built-in app as aimed at home users and not its recommended installation method [2]. In practice it also runs on small-organisation servers, as the issue thread shows [3].
What to do
- Inventory every Nextcloud instance for the Collabora Online Built-in CODE Server app. Upgrade to 26.4.303 or later, or remove the app. Do not rely on disabling it [1][2].
- On Nextcloud 29 or earlier, upgrade Nextcloud first or remove the app. The fixed release requires a supported Nextcloud version [1][4].
- Treat any instance that ran 26.4.302 or earlier while internet-facing since early September as possibly compromised. Run Nextcloud’s integrity check, look for unexpected PHP files in the app’s directory and review web logs for requests to the app from 10 September onward [3][4].
- Rotate secrets readable by the web server account. That includes database credentials, LDAP bind credentials and any credential stores on the host. Upgrading does not remove a web shell that is already in place [3][5][10].
- Where an office suite is needed, move to a standalone Collabora Online deployment, which is unaffected [1][2].
- For self-hosted, internet-facing applications, track upstream release notes and issue trackers as well as CVE and KEV feeds. Treat an unexplained security release as an advisory in its own right [2][11].
- Do not assume that dependency scanners cover application plug-ins. The GitHub Advisory Database entry here carries no package or version data [6].
The offensive security view
Attackers had the patch before defenders had an identifier. A public fix commit, a version bump and a GitHub issue are enough for a capable operator to find the vulnerable path. None of those artefacts reaches a CVE-driven vulnerability programme. GitHub’s own figures show CVE publication slowing as report volumes rise [11]. Collabora’s response is to become a CNA and publish directly [2]. Until more maintainers can do the same, the fix-to-CVE interval is real attack surface. It should be measured and monitored like any other exposure window. Red teams assessing self-hosted collaboration stacks should check bundled helper apps and their proxy endpoints as a matter of course. The two CVEs in this proxy in under a year are a reminder of why [1][12].
Sources
Every R3KONX article cites its primary material. 14 sources, in order of first citation. Links open the original publication.
- Unauthenticated OS command injection in the richdocumentscode proxy (GHSA-g3vx-3m76-fghh, CVE-2026-110447) Collabora Online (GitHub security advisory) · 2026-10-14
- Stay safe: upgrade everything regularly Collabora Productivity · 2026-10-15
- richdocumentscode issue #354: Security issue - Hack CollaboraOnline/richdocumentscode (GitHub) · 2026-09-11
- To Collabora Built-in user: update ASAP Nextcloud community forum · 2026-10-03
- occ-Missbrauch durch richdocumentscode 26.4.302? Nextcloud community forum · 2026-09-23
- GHSA-f97p-r72q-64h2: Collabora Online Built-in CODE Server before 26.4.303 GitHub Advisory Database · 2026-10-14
- CVE-2026-110447 record and change history OpenCVE · 2026-10-26
- Exploited CVEs: CVE-2026-110447 Senserva · 2026-10-23
- U.S. CISA adds Collabora Online flaw to its Known Exploited Vulnerabilities catalog Security Affairs · 2026-10-24
- Hackers exploit Collabora RCE flaw to backdoor Nextcloud servers BleepingComputer · 2026-10-15
- Inside the Advisory Database, and what happens when vulnerability volume breaks records GitHub Blog · 2026-06-29
- Security advisories: CollaboraOnline/online Collabora Online (GitHub) · 2025-12-03
- CVE-2025-66208 INCIBE-CERT · 2025-12-03
- Collabora Online flaw exploited to attack Nextcloud servers iThome · 2026-10-19
Researched and written by the R3KONX analysis desk from the cited primary material. The CISA KEV entry and alert on cisa.gov could not be retrieved; the 23 October addition date and 26 October due date are taken from Senserva's KEV mirror, OpenCVE's record history and Security Affairs. The 9 September fix commit and 11 September release dates are as reported by BleepingComputer and were not independently confirmed from the repository. Attack observations come from administrator reports in public issue and forum threads, not from vendor telemetry. Corrections to event@r3konx.asia.
