The short version
- The flaws. CVE-2026-105133 is an authentication bypass with a public exploit and CVE-2026-105134 allows OS command injection. Chained, they give unauthenticated remote code execution on the AhsayCBS backup management server.
- The attacks. Huntress says it saw the two bugs exploited in the wild from 7 October to deploy Java Server Page webshells and XMRig cryptominers. At least five organisations had been targeted as of 8 October.
- Patches fell short. The flaws were believed fixed in AhsayCBS 9.15.2.59 and 10.3.4.0, released in August 2026, but Huntress found 10.3.4 still vulnerable. Ahsay has now confirmed the earlier patches were incomplete and issued hotfixes 10.3.4.45 and 9.15.2.70.
- Official response. CISA has added both flaws to its Known Exploited Vulnerabilities catalogue, with a 17 October 2026 deadline for US federal agencies to patch. BleepingComputer said Ahsay had not answered its questions about the flaws at the time of publication.
- What defenders should do. Huntress advises limiting access to the AhsayCBS management interface to trusted IP addresses or a VPN, checking for signs of compromise and, where a host is confirmed compromised, restoring it from a clean backup.
Timeline
| Date | Event |
|---|---|
| 4 October | The two flaws are disclosed after NIST warns that exploit code has been released and that all AhsayCBS versions up to 10.3.2 are affected. |
| 7 October | Huntress observes attackers exploiting the flaws to deploy webshells and cryptominers. |
| 8 October | At least five organisations have been targeted, according to Huntress. |
| 15 October | By 15 October: Ahsay has released hotfixes 10.3.4.45 and 9.15.2.70 and confirmed its August patches did not completely fix the flaws. |
| 17 October | Deadline set by CISA for US federal agencies to apply the patches. |
How the attacks worked
Huntress says attackers used CVE-2026-105133 to bypass authentication and then CVE-2026-105134 to inject and run operating system commands. One route is an API in the Replication Receiver component, where a random token can substitute for valid credentials. After that, the attackers set up a malicious receiver and dropped a Java Server Page webshell into the application directory served by AhsayCBS.
Once inside, they carried out reconnaissance and installed the XMRig cryptocurrency miner disguised as edge.exe. Persistence came from a Windows service named MicrosoftEdgeUpdateSvc running msedge.exe, which Huntress identified as a modified copy of the legitimate NSSM utility that keeps programs running and restarts them after a crash or reboot.
A PowerShell script, Taskgmr.ps1, which Huntress believes was AI-assisted, hides the mining by stopping and restarting the service as Task Manager opens and closes, and terminating Task Manager at 6pm local time or if it remains open for more than an hour overnight. In one case the attackers also loaded WinRing0x64.sys, a legitimate but vulnerable kernel driver, likely to give the miner more hardware access.
Who is affected
AhsayCBS is a central management console for backup policy, storage and user administration, and is popular with managed service providers and system integrators.
NIST said on 4 October that all versions up to 10.3.2 were affected. Huntress later found the flaws still worked on 10.3.4, then the latest release. The company has since published hotfixes for the 10.3.4 and 9.15.2 branches; it says administrators should reboot the server after applying them, and Huntress says it independently verified that the 10.3.4.45 hotfix mitigates the initial entry point of the attack chain.
Patch history and official response
AhsayCBS 9.15.2.59 and 10.3.4.0, released in August 2026, were initially treated as the fixes. Ahsay has now confirmed they did not completely plug the two flaws, and its advisory urges customers to act immediately to secure their environments and protect their customers' data. Huntress has published indicators of compromise and four Sigma detection rules for the activity.
CISA added both vulnerabilities to its Known Exploited Vulnerabilities catalogue, which sets a binding patch deadline for US federal agencies. BleepingComputer said it had asked Ahsay about its plans to fix the flaws and had not received a reply by publication; the later reporting does not say what changed at the company between the two dates.
What is not known yet
- Who carried out the attacks, and whether the same actor is behind every observed intrusion.
- How many organisations were compromised in total, beyond the five Huntress reported by 8 October.
- Whether the attackers accessed or copied backup data from affected systems, rather than only using their processing power.
- Whether the 10.3.4.45 and 9.15.2.70 hotfixes close both flaws completely; Huntress says it verified only the initial entry point on version 10.
- Whether installs on older branches, or versions earlier than 9.15.2, are exposed and have a fix available.
What to do
If you run AhsayCBS
- Apply hotfix 10.3.4.45, or 9.15.2.70 on the 9.15.2 branch, and reboot the server afterwards.
- Restrict access to the AhsayCBS management interface to trusted IP addresses only, or require a VPN; the exploit targets the web service on the host.
- Hunt for the published indicators of compromise, including the MicrosoftEdgeUpdateSvc service, edge.exe, Taskgmr.ps1 and dropped JSP webshells, and deploy Huntress's Sigma rules.
- If a host is confirmed compromised, restore it fully from a clean backup, because additional backdoors may have been installed.
If an MSP or integrator runs your backups
- Ask whether your provider uses AhsayCBS and has applied the new hotfix.
- Ask whether its management interface is reachable from the internet, and request that access be limited to trusted addresses or a VPN.
For everyone else
- Keep management consoles for backup and other infrastructure off the public internet wherever possible.
- Do not treat a vendor's first patch release as final: check for a reissued advisory or hotfix before closing an incident.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.