A serious vulnerability in our Built-in Collabora Online Developer Edition (CODE) PHP server app for Nextcloud was discovered and patched a month ago, and this has now been disclosed.
Further to our recent security advisory, and Nextcloud’s contemporary advice to upgrade, we are advising anyone who has the Nextcloud Built-in CODE Server app (which is focused on home users) to upgrade immediately to 26.4.303 or later due to the impact of this issue.
While serious, the scope of the exploit is narrow, it affects only the optional Nextcloud Built-in CODE server app, which is not Collabora’s recommended installation method and is used by a minority of Nextcloud users.
The attack also only work if the built-in CODE server is not running, such as during the window while a container restarts, during an upgrade, or after a crash.
No Collabora Online customers were affected and we must stress this vulnerability was fixed a month ago. If you use docker images, RPM/DEB packages, or the Nextcloud All-in-one images you are unaffected.
A month ago, Nextcloud encouraged all of the Nextcloud Built-In CODE Server users to “Get your update right now” after the fix was released—which also had an extra benefit: by upgrading users gained the new Landlock security feature which gives every deployment a stronger, kernel-enforced sandbox as well.
Our security team is continually working to defend the security of our customers and community. All users of all software should be aware of the extremely high volume of AI-driven security auditing reports of varying quality—and the significant load this is placing on vendors of all software. This year we have reviewed, processed, fixed and shipped around ten years’ worth of security reports so far. This unfortunately has put significant strain on the CVE process. The time required to get a GitHub CVE filed and published has gone from around a day to many weeks this year. We are, of course, grateful to GitHub, who are doing sterling work under an extreme workload from huge numbers of Open Source projects.
This was clearly the main factor in getting the fix formally announced in a timely way, and we are applying to improve the responsiveness of this process by going direct and becoming a CNA.
In any event, we encourage everyone to update all of their software very regularly, at this time— and to take any vendor advice to update extremely seriously and promptly. We are also extremely grateful to those who engage constructively with the security disclosure process—thank you for your support, and we will credit you eventually when we can. Thanks too to Nextcloud for their prompt assistance.