On 8 October 2026, the managed detection and response firm Huntress reported that attackers were chaining two vulnerabilities in AhsayCBS, the server console behind Ahsay’s backup software, to run commands on internet-facing backup servers with full SYSTEM privileges. The flaws, CVE-2026-105133 (an authentication bypass) and CVE-2026-105134 (an OS command injection), had been published four days earlier, together with a warning that exploit code was already public. Huntress saw the first attack late on 7 October and counted five targeted organizations by the next day. The intruders planted web shells (scripts that give remote control of a server through its web interface) and a disguised cryptocurrency miner.
The more uncomfortable part of the story is what “patched” meant. Ahsay, which The Hacker News describes as Singapore-based, had shipped versions 9.15.2.59 and 10.3.4.0 in August, and those builds were initially assumed to cover the two flaws. On 10 and 12 October the vendor confirmed that they did not. Operators who had done the right thing in August were still exposed in October. AhsayCBS is used mainly by managed service providers (MSPs) and system integrators, so the businesses whose data sits on these servers are often a step removed from the people who patch them.
What happened
- August 2026: Ahsay releases AhsayCBS 9.15.2.59 and 10.3.4.0. According to The Hacker News, these versions were at first assumed to address both vulnerabilities.
- 4 October: The two CVEs are published. SecurityWeek reports that NIST warned at disclosure that exploit code had been released and that all versions up to 10.3.2 were affected.
- 7 October, 23:20 UTC: Huntress begins seeing exploitation. Attackers first use CVE-2026-105133 to get past authentication, then CVE-2026-105134 in the Replication Receiver API to execute code.
- 8 October: Huntress publishes its analysis. In an evening update it adds that version 10.3.4 is also affected: “Previous reporting indicated that 10.3.4 was not susceptible; we have updated this writeup to reflect our findings.”
- 9 October: Ahsay begins receiving reports from partners of unauthorized access to their AhsayCBS servers, according to the vendor’s status update. BleepingComputer reports that it asked Ahsay about a fix and had no reply at publication.
- 10 October: Ahsay issues a critical security alert stating that “our previous patch v10.3.4.0 did not fully address” the two CVEs, and tells partners on version 10 to apply hotfix 10.3.4.45 and reboot.
- 12 October: An updated alert adds that 9.15.2.59 was also incomplete and releases hotfix 9.15.2.70 for versions 7, 8 and 9. Huntress says it has independently verified that 10.3.4.45 mitigates the initial entry point of the attack chain.
- 13 October: Ahsay publishes indicators of compromise and recovery steps.
- 14 October: CISA adds both flaws to its Known Exploited Vulnerabilities (KEV) catalog. US federal civilian agencies were given until 17 October to remediate, The Hacker News reports.
What the attackers did once inside
Huntress first noticed suspicious command lines spawned by the AhsayCBS service executable, cbssvcX64.exe. In some cases the attacker configured a malicious replication receiver and dropped a JSP web shell into the directory the CBS web application serves. In others, the service downloaded files into Temp folders from Alibaba Cloud object storage: an XMRig Monero miner renamed edge.exe, a modified copy of the NSSM service manager renamed msedge.exe, a configuration file and a PowerShell script.
Persistence came from a Windows service called MicrosoftEdgeUpdateSvc, named to look like the real Edge updater and running with SYSTEM privileges. The script, which Huntress believes was written with AI assistance, stops the miner whenever Task Manager is open and kills Task Manager at 18:00 or if it stays open for more than an hour overnight. In one incident the attacker also loaded WinRing0x64.sys, a legitimate but vulnerable kernel driver, to give the miner low-level hardware access. Huntress’s indicator list includes IP addresses registered in Hong Kong, Vietnam, Taiwan, France and the United States. No source has named the group responsible.
Why it matters
A backup server is a control point, not a storage box. Huntress notes that AhsayCBS centralizes control of backup operations, letting administrators create users and set backup policies. For an MSP, one such server can hold the backups of many client companies. A miner is a noisy and fairly cheap use of SYSTEM access to that machine. The same foothold could be used to read, alter or delete the copies a business plans to restore from after a ransomware attack, which is why Ahsay’s own alert urges partners to “protect your customers data.”
A version number is not proof of a fix. Administrators who installed 10.3.4.0 in August had every reason to believe they were covered, and early coverage after disclosure still said 10.3.4 was safe. It took Huntress’s testing and two vendor alerts to establish that the safe builds were 10.3.4.45 and 9.15.2.70. Any patch record that says “upgraded to the latest version” without naming the build needs to be checked again.
The window was days. Exploit code was public when the CVEs appeared on 4 October, and attacks started less than four days later. Because the vendor’s earlier fix was incomplete, a working hotfix arrived only on 10 October for version 10 and on 12 October for older versions. During that period, the only effective control was keeping the management interface off the public internet.
Patching does not remove an intruder. CISA’s KEV notice points to Binding Operational Directive 26-04, which “further establishes basic expectations for when agencies must check whether threat actors compromised the system before the patch was applied.” Huntress and Ahsay both go further and recommend rebuilding compromised hosts; Huntress notes that attackers have been able to hide secondary backdoors for extended persistence, which a hotfix will not touch.
For small and mid-sized businesses in Vietnam and across Southeast Asia, the practical exposure often sits with a provider. Many companies buy backup as a service from an integrator or MSP and never see the server that holds their data. That makes this a vendor-management question as much as a patching one.
Questions to put to your backup provider this week
- Do you run AhsayCBS, or any other backup console, on our behalf?
- Which exact build is installed today, and when was hotfix 10.3.4.45 or 9.15.2.70 applied?
- Is the management interface reachable from the internet, or only from trusted addresses or a VPN?
- Have you checked the server against Ahsay’s and Huntress’s indicators, and what did you find?
- If the server was compromised, was it rebuilt, and have you confirmed that our backups are intact and restorable?
What to do now
- Find every AhsayCBS instance. Include servers you operate, servers your MSP or integrator operates for you, and test or disaster-recovery copies that may have been forgotten.
- Check the build, not the ticket. Version 10 servers need hotfix 10.3.4.45 or later; versions 7, 8 and 9 need 9.15.2.70, and Ahsay advises v7 and v8 operators to upgrade to 9.15.0.0 first. Ahsay says the server must be rebooted after the hotfix.
- Take the management interface off the internet. Huntress recommends limiting web access to trusted IP addresses or requiring a VPN. Do this even after patching.
- Hunt for compromise back to at least 4 October. Ahsay lists four indicators: unexpected folders at the root of drives (for example
ahsay_ts,ahsay_t8,ahsay_t20,srv,useroropt); randomly named.jspfiles or short random folders in%CBS%\webapps; unauthorized replication (RPS) receivers; and unauthorized AhsayCBS accounts with Admin privileges. Huntress adds process-level signs: child processes ofcbssvcX64.exe, aMicrosoftEdgeUpdateSvcservice,edge.exeormsedge.exein Temp folders, theWinRing0x64.sysdriver, and outbound connections on port 8029 to mining pools. - Rebuild, do not clean. If any indicator is present, follow Ahsay’s procedure: reinstall the operating system, install AhsayCBS 9.15.0.0 or 10.3.4.0 and apply the matching hotfix, then restore the server configuration from an Auto Save version dated at least a day before the earliest suspicious file. Rotate every credential the server held, including administrator accounts and access to backup storage.
- Prove the backups still work. Run a test restore of critical systems, and keep at least one copy that cannot be modified or deleted from the same console.
- Write it into the contract. For outsourced backup, set a deadline for applying fixes to actively exploited flaws, require the installed build as evidence, and require prompt notice of any suspected compromise of the backup platform.
Era Artech’s perspective
Backup is usually the last line of defense in a ransomware plan, which also makes the backup console one of the most valuable systems to an attacker. The AhsayCBS case shows two habits worth adopting: treat any management interface exposed to the internet as a short-lived exception, and record a fix as complete only when the exact build has been verified and a compromise check has been done. When a provider runs the platform, the business still owns the question of whether its backups can be trusted.