OFFSEC · Offensive Security

AhsayCBS exploitation: the advisory records said 10.3.4 was safe, and it was not

Two chained flaws in a backup console used widely by managed service providers were exploited for at least a week while the CVE record, a vulnerability database and the vendor's own first clarification pointed defenders at a build that did not close them. The miners were the visible payload; at least one operator went further.

The record said patched

For at least a week in October, a defender who checked an AhsayCBS server against the public vulnerability record would have been told it was safe on version 10.3.4. It was not. Attackers chained two flaws in the backup console, an authentication bypass and an OS command injection in the Replication Receiver component, to run commands as SYSTEM without credentials [1]. Huntress first saw exploitation at 23:20 UTC on 7 October 2026, three days after the CVEs were published [1].

The CVE record describes the flaws as affecting AhsayCBS up to 10.3.2 and lists 10.3.4 as unaffected; that entry was last modified on 15 October [7]. VulDB, the CVE Numbering Authority, still states that upgrading to 10.3.4 eliminates the command injection after its last update on 14 October [6]. Debian’s tracker carries the same mitigation text for the authentication flaw [8]. Ahsay itself says the opposite: its 12 October update states that patches 9.15.2.59 and 10.3.4.0 “did not fully address” either vulnerability [3].

This is the argument for practitioners. The exploitation is ordinary. The failure is in the remediation signal, and it affects every tool and process that trusts the CVE record for affected-version data.

What the data says

Version 10.3.4 shipped on 5 August 2026. Its release notes list no security fixes and name no CVEs [5]. The CVEs appeared in the record on 4 October with a note that a public exploit existed [2][15]. On 8 October Huntress updated its report to say 10.3.4 was also affected and that it had contacted Ahsay [1].

Ahsay’s announcements page shows how the vendor position moved. A 9 October clarification said upgrading to 10.3.4.0 protected against remote exploitation. Alerts on 10 and 12 October reversed that and directed partners to hotfix 10.3.4.45 for v10 and 9.15.2.70 for v7, v8 and v9, both behind the partner portal and both requiring a reboot [3][4]. A 13 October status update added compromise indicators and recovery guidance [4][9]. The vendor has not said why the August build fell short [2].

Hotfix dates differ between sources. Hive Security, citing Ahsay’s status report, gives 10 October for the v10 hotfix and 12 October for v9 [9]. Bitdefender gives 12 October for both [2]. Daily Security Review reports the new hotfixes alongside the 14 October KEV listing [14]. Huntress says it independently verified that 10.3.4.45 mitigates the initial entry point [1]; no reviewed source independently verifies the v9 hotfix [9][14].

Severity also differs. The CNA scores the command injection at 10.0 under CVSS 4.0 and 3.1; the NVD record and several advisories list 9.3 under CVSS 4.0 [7][2][13]. The authentication flaw is rated 7.3 under CVSS 3.1 and 5.5 under CVSS 4.0 [2]. The chain matters more than either score.

Two responder datasets describe the activity. Huntress reported five organisations targeted as of 8 October, and later told The Hacker News it had seen one further incident with the same techniques [1][13]. eSecurityPlanet notes that five targeted organisations are not necessarily five confirmed breaches [10]. Huntress observed JSP webshells, a Monero miner disguised as a browser binary, a masquerading Windows service for persistence, a script that paused mining while Task Manager was open, and in one case a vulnerable kernel driver loaded to give the miner hardware access [1][12].

Bitdefender MDR investigated three separate incidents from around 7 October [2]. All began with the same chain. Beyond webshells, it saw PowerShell staged on a public static-hosting service, attempts to survive reboots and password changes, a search for stored credentials, a user elevated to SYSTEM, and OpenSSH installed to give a second access path independent of the web service [2]. It saw no encryption, exfiltration or ransomware, and assesses that several actors may be using the same exploits, with some shared infrastructure in two incidents [2]. Its post-exploitation picture differs from Huntress’s; the datasets may overlap and neither names an actor.

What it means

A backup console is a high-value position. SecurityWeek and BleepingComputer describe AhsayCBS as popular with managed service providers and system integrators [11][12]. Field Effect notes that a single instance can manage multiple customers, sites or business units, and that a compromised server gives SYSTEM-level control of the host and its credentials, storage locations and repositories [15]. No reviewed source reports theft of backup data [9][14]. That is an absence of evidence in a short window, not an assurance.

The cryptominer is the visible payload, not the ceiling. Bitdefender’s observation of credential searching and an out-of-band SSH path is the pattern of an operator preserving access, and it warns that dormant footholds can be resold or used later [2]. Unit 42’s September ranking puts exploitation of public-facing applications first among initial access vectors and pairs it with credential abuse [16].

The records problem will recur. Rescana advises treating any vendor answer of “10.3.4” in third-party risk reviews as an open item [17]. Scanners and asset tools that resolve exposure by matching a minor version against CVE data will report these servers as clean.

What to do

  • Inventory every AhsayCBS instance, including disaster recovery, test and provider-hosted servers, and record the full build number; 10.3.4.0 and 9.15.2.59 are vulnerable according to Ahsay [2][3][15].
  • Override scanner and CMDB logic that treats 10.3.4 as fixed for these CVEs until the CVE record and VulDB entries are corrected [6][7].
  • Apply 10.3.4.45 or 9.15.2.70 and reboot; v7 and v8 servers move to 9.15.0.0 first, per Ahsay’s status report [3][9].
  • Restrict the management web service and Replication Receiver to administrative networks or VPN, and confirm the restriction at the actual exposed path, including NAT and firewall rules [1][2][9].
  • Hunt from 4 October onwards, on patched servers too: unknown JSP files in the web application directories, shells spawned by the AhsayCBS service, unexpected replication receivers or administrator accounts, new services, and OpenSSH on hosts that never used it [2][4][9].
  • Deploy Huntress’s published behavioural detections after validating them against local maintenance activity [1][9].
  • If indicators are present, rebuild the server, restore configuration from a point before the intrusion, and rotate credentials stored on or reachable from it, including storage destination and service accounts [2][4].
  • MSPs should notify downstream customers whose backups the console managed and test restoration of a representative workload in isolation [9][15].

The OFFSEC read

The exploit chain is not novel. What made it effective was a remediation record that pointed defenders at a build that did not fix the flaws, and a vendor clarification that reinforced it for a day [3][4][7]. For edge and management software, the build number is the unit of truth, and the CVE record’s affected-version field is a claim to verify. Teams that track exploitation by CVE status alone would have closed this ticket against a build installed in August.

Sources

Every R3KONX article cites its primary material. 17 sources, in order of first citation. Links open the original publication.

  1. Threat Actors Exploit Critical AhsayCBS Flaws to Drop Webshells and XMRig Cryptominer Huntress · 2026-10-08
  2. Technical Advisory: AhsayCBS Exploitation Chain (CVE-2026-105133, CVE-2026-105134) Bitdefender · 2026-10-15
  3. (Update) Critical Security Alert: Immediate Action Required for CVE-2026-105133 and CVE-2026-105134 Ahsay Systems · 2026-10-12
  4. Announcements Ahsay Systems · 2026-10-13
  5. AhsayCBS v10.3.4 Release Notes Ahsay Systems · 2026-08-05
  6. VDB-413351: Ahsay AhsayCBS Replication Receiver OS command injection (CVE-2026-105134) VulDB · 2026-10-14
  7. CVE-2026-105134 OpenCVE (CVE and NVD record mirror) · 2026-10-15
  8. CVE-2026-105133 Debian Security Tracker · 2026-10-04
  9. AhsayCBS Under Attack: When the Backup Server Becomes the Foothold Hive Security · 2026-10-14
  10. Ahsay Confirms Failed Patch for Two Exploited Backup Flaws eSecurityPlanet · 2026-10-11
  11. Unpatched AhsayCBS Vulnerabilities Exploited in the Wild SecurityWeek · 2026-10-09
  12. Unpatched AhsayCBS flaws exploited to deploy webshells, mine crypto BleepingComputer · 2026-10-09
  13. Attackers Exploit AhsayCBS Flaws to Deploy XMRig Miners Disguised as Microsoft Edge The Hacker News · 2026-10-09
  14. Ahsay Issues New AhsayCBS Hotfixes After Earlier Patches Failed Daily Security Review · 2026-10-15
  15. Threat actors exploit AhsayCBS zero-days Field Effect · 2026-10-09
  16. Top 5 Initial Access Threat Vectors Observed by Unit 42 in September 2026 Palo Alto Networks Unit 42 · 2026-10-16
  17. AhsayCBS CVE-2026-105133 / CVE-2026-105134 exploited: backup console RCE Rescana · 2026-10-12

Researched and written by the R3KONX analysis desk from the cited primary material. Methodological caveat: incident counts come from two separate responder datasets (Huntress and Bitdefender MDR) that may overlap and do not measure the exposed population, and no source reviewed gives a count of internet-reachable AhsayCBS servers. Corrections to event@r3konx.asia.

R3KONX 2027

Work in this domain? So does the programme

4–6 May 2027, World Trade Centre Kuala Lumpur. Curated talks, hands-on training and The BattleGrid.