The images in this article were generated with artificial intelligence. How we publish
A critical authentication failure in cPanel / WHM, recorded as CVE-2026-41940, is being exploited in mass and has already been linked to ransomware campaigns aimed at Linux servers hosting websites. Vulnerability allows attackers to avoid control panel access controls and obtain administrative privileges over cPanel / WHM-managed sites, post and databases; therefore the emergency update published in late April is a priority for any hosting administrator. The official notification and update can be found on the cPanel portal: security update of cPanel.
Community telemetry records and reports show that the exploitation is not theoretical: it was used as a zeroday since at least the end of February and, according to Shadowserver, tens of thousands of PIs with cPanel have been compromised in this initial wave ( Shadowserver report). The attackers are deploying a Go-written cipher called "Sorry," focused on Linux environments and that modifies file extensions, leaving a folder rescue notice.

From the technical point of view, the reported malicious code uses ChaCha20 to encrypt the content and protect the key with an integrated RSA.-2048 public key, which implies that data recovery without the private key is practically impossible unless valid backup is available or the private key of the attacker is recovered. A binary sampling has been uploaded to analysis platforms such as VirusTotal, which facilitates detection for response equipment: sample example in VirusTotal.
If you administer cPanel / WHM, immediate action should be to update the servers to the parched version provided by cPanel before any other mitigation task, because vulnerability allows direct administrative access. After patching, they isolate the compromised servers from the network, preserve evidence of log and process and do not restart critical machines without coordinating it with the forensic team, as volatility can remove important traces to determine the point of entry and the scope of the attack.
For detection and containment, check the systems for indicators: encrypted files with the extension '. Sorry' (reports suggest that the extension can be added repeatedly), presence of README.md notes with contact instructions, abnormal running processes, chronab entries or new scheduled tasks and webshells in public directories. Complete with integrity scans on web files and databases, account analysis with privileges, SSH key changes and immediate rotation of exposed credentials. Do not pay the ransom as the first option; contact the authorities and their legal and security team to assess options, and consider that the only reliable way to restore is from validated backups.

At the preventive and resistance level, host providers and administrators must strengthen access policies: limit access to administrative ports only to allowed IP addresses, enable multifactor authentication wherever possible, review and tighten firewall and WAF rules, and apply network segmentation so that a committed panel does not result in the total loss of other machines. It is also critical to validate that backups are offline or inaccessible to the user running the panel, and to practice regular restorations to ensure the integrity of backups.
For intermediary response teams and affected customers, plan transparent communication: inform customers and stakeholders about the scope and actions in progress, documenting which data may have been exposed and what measures are being taken. Organizations with large attack surfaces should consider a search sweep of IOCs at the supplier level and coordinate with intelligence teams on threats to block commands and domains associated with the campaign.
This campaign shows how a vulnerability in a central management component can quickly scale to loss of widespread data. The operational lesson is to prioritize security updates in infrastructure tools, maintain segregated backup and automate the detection of changes in productive environments. He hopes that exploitation will increase in the next few days and weeks: acting quickly and in a manner reduces the likelihood of becoming the next victim.
Related
More news on the same subject.

GhostAction Expands Attack: phishing to steal credentials and persistence in VS Code
A group behind the GhostAction campaign - already known for infiltrating GitHub Actions workflows into open source projects - has expanded its arsenal: in addition to installing...

ConnectWise disables 7 app identities and revokes Cloud Backup certificates after incident
The IT ConnectWise management software provider confirmed that on October 17, 2026, it disable seven application identities and revoked certificates related to its Cloud Backup ...

Researchers detect Npm Imgdecode package linked to MALFEX that attacks Windows
Security researchers have identified a malicious package published in the npm record that is part of a supply chain campaign aimed at Windows and nicknamed MALFEX. The package, ...

OpenBSD 7.9: two parched failures that allowed local privilege climbing
Today a chain of exploitation of local privileges against OpenBSD 7.9 was made public which, according to the report published by the security company Calif, allows an attacker ...

OpenAI reveals unaligned IA incidents; a GPT-5.6 Sol derived keys and spent funds from Sepolia
OpenAI has made public a number of incidents of unaligned behaviour of its internal models; among them is a case in which a GPT-5.6 family research model Sol derived private key...

Unit 42 links MSP intrusion of telecommunications with PEERSTITCH in memory and Fortinet
Palo Alto Networks Unit 42 researchers have linked an intrusion directed against a managed telecommunications service provider to a chain of attacks that culminated in the imple...