As reported by BleepingComputer, threat actors are actively chaining two vulnerabilities in the AhsayCBS backup management platform — CVE-2026-105133 (authentication bypass) and CVE-2026-105134 (OS command injection) — to deploy webshells and cryptocurrency miners across at least five organizations. The most alarming detail: Ahsay 10.3.4, the latest version, remains vulnerable despite earlier reports that 10.3.2 resolved the issues. No patch is currently available.

Security Impact: As reported by BleepingComputer, threat actors are actively chaining two vulnerabilities in the AhsayCBS backup management platform — CVE-2026-105133 (authentication bypass) and CVE-2026-105134 (OS command injection) — to deploy webshells and cryptocurrency miners across at least five organizations.

Vulnerability Summary

CVETypeSeverityStatus
CVE-2026-105133Authentication bypassCriticalUnpatched in 10.3.4; public exploit available
CVE-2026-105134OS command injectionMediumUnpatched in 10.3.4

Affected vendor: AhsayCBS (Ahsay Online Backup)
Affected versions: 10.3.2 through 10.3.4 (latest)
Patch available: No — vendor has not responded to inquiries
Active exploitation: Yes — observed October 7, 2026
Primary targets: MSPs and system integrators

Why This Matters

This incident underscores a recurring nightmare for the MSP ecosystem: backup platforms are high-value targets because they hold privileged access to customer environments and often run with elevated permissions. When the very tool meant for recovery becomes the entry point, attackers gain a foothold that can ripple across dozens of downstream clients.

The attack chain is textbook but effective. Authentication is bypassed via CVE-2026-105133, giving the attacker a foothold without credentials. CVE-2026-105134 then provides arbitrary command execution. From there, the threat actor deploys JSP webshells for persistent access and drops XMRig — disguised as edge.exe — with a clever persistence mechanism using NSSM wrapped as a fake MicrosoftEdgeUpdateSvc service. A PowerShell script (likely AI-generated, per Huntress analysis) actively evades detection by killing the miner when Task Manager opens and restarting it when Task Manager closes.

The fact that the latest available version remains exploitable — with no vendor acknowledgment — means organizations cannot simply upgrade their way out of this. Network-level isolation is the only viable mitigation right now.

Who Is at Risk

Why This Matters
MSPs and system integrators running AhsayCBS with internet-exposed management interfaces are the highest-risk group.
Organizations with AhsayCBS 10.3.2–10.3.4 are confirmed vulnerable regardless of version currency.
Environments where AhsayCBS runs with elevated privileges face lateral movement risk beyond the initial host compromise.
Bring-your-own-vulnerable-driver (BYOVD) exposure — the deployment of WinRing0x64.sys suggests the attacker may attempt kernel-level resource hijacking for more aggressive mining.

Shield53 Recommendations

Immediate Actions

  • Isolate the AhsayCBS management interface from the public internet immediately. Restrict access to a VPN or a allowlist of trusted internal IP addresses. This is the single most critical mitigation until a patch is released.
  • Deploy Huntress Sigma rules and IoCs to your SIEM/EDR for detection of webshell deployment, the fake MicrosoftEdgeUpdateSvc service, and edge.exe / msedge.exe (NSSM wrapper) artifacts.
  • Hunt for JSP webshells in the AhsayCBS installation directory and web application paths. Any unexpected .jsp files should be treated as hostile.
  • Check for the Taskgmr.ps1 script and any PowerShell scripts monitoring Task Manager process state — this is a strong indicator of the specific campaign.
  • Audit for WinRing0x64.sys and other kernel-mode drivers loaded outside of normal update channels.
  • If compromise is confirmed: perform a full bare-metal restore from a known-good backup. Do not attempt to clean in place — additional backdoors may have been installed that are not yet identified.
  • Monitor vendor channels for a patch announcement and apply it immediately upon release. Given the vendor's silence, do not assume a fix is imminent.

Strategic Considerations

For MSPs, this incident reinforces the need for a vendor risk management program that includes monitoring of backup platform vulnerabilities and contractual expectations for patch SLAs. When a critical vulnerability goes unpatched with no vendor communication, escalation paths — including pre-positioned migration plans — should already exist. Additionally, the likely AI-assisted PowerShell evasion script signals that threat actors are increasingly leveraging generative AI to produce detection-resistant tooling, a trend defenders should factor into their detection engineering and threat hunting programs.