Hackers exploit Collabora flaw to backdoor Nextcloud servers

Started by RicFlair04, Oct 26, 2026, 04:36 PM

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Topic: Hackers exploit Collabora flaw to backdoor Nextcloud servers   Views(Read 32 times)

RicFlair04

Attackers are exploiting a critical flaw in an optional Collabora Online component for Nextcloud, the popular self hosted file sharing platform. BleepingComputer reports that the bug affects the built in CODE Server app before version 26.4.303. It allows a malicious request to run operating system commands without any login or user interaction

There is a specific condition. The attack works when the built in server is stopped, for example after a restart or a crash. Attackers have used it to plant PHP web shells, giving them ongoing access, and to search for password databases, password manager files and crypto wallets

The timeline is frustrating. Attacks began around 10 September. Collabora committed the fix on 9 September and shipped it on 11 September, but the security advisory and CVE identifier only came out on 14 October. That meant many administrators had no clear warning for a month while the flaw was being exploited

Collabora blamed backlogs in GitHub's CVE process, which have grown because of a flood of AI generated bug reports. A study by Second Security found that the median gap between a fix and its CVE grew from 5.1 days in January to 39 days in August. That is a worrying trend for everyone who relies on advisories to know when to patch

Administrators should upgrade or remove the app, because simply disabling it is not enough. Some users have claimed ransomware gangs are involved, although BleepingComputer could not confirm that. Self hosting gives control, but it also means taking responsibility for security updates

How do you keep up with security updates for self hosted software? And what should be done about the growing CVE backlog?


Janette_63

Automatic updates would have saved a lot of people here. Many self hosters disable them to avoid breakage. That trade off looks worse after this. Breakage is a real worry with Nextcloud updates. Apps sometimes stop working after major versions

Still, a security patch is worth the risk. Snapshots before updating make it safer

Arrow56

Hunting for password managers and crypto wallets shows the attackers knew exactly what they wanted. Valuable data stored on file servers is a big risk. Wallet files sitting on a shared drive are a gift to attackers

Encryption at rest would have helped. Many home setups skip it
Hot take: most AI problems are data problems wearing a fancy hat.

Ridge66

Simply disabling the app not being enough is an important detail. Many admins would assume that was safe

Upgrade or remove is clear advice. Plenty of people would have switched it off and moved on. That would have left them exposed. Clear advisories prevent mistakes like that

Glenn83

Watching commit logs for security fixes is a common attacker technique. Open source makes fixes public immediately. Advisories need to keep up

Defenders need the same speed. Automated alerts on security commits would help

Socket91

The CVE backlog growing from five days to 39 is alarming. AI generated bug reports are clogging the system. Something needs to change in how reports are triaged

Triage tools could help filter out low quality submissions. Some projects have started banning AI generated reports entirely

Neither approach is perfect. The backlog keeps growing in the meantime