In this article
Patch summary
- CVE
- CVE-2026-105133, CVE-2026-105134
- Exploited?
- Yes. Huntress says it began seeing exploitation of CVE-2026-105133 and CVE-2026-105134 on October 7, 2026, at 23:20:15 UTC, and had seen five organizations targeted as of October 8. Ahsay says it began receiving partner reports of unauthorized access to AhsayCBS servers on October 9, 2026. CISA added both CVEs to its Known Exploited Vulnerabilities catalog on October 14, 2026, with a due date of October 17, 2026.
Affected products and patches
| Product | Affected | Patch | Source |
|---|---|---|---|
| AhsayCBS v10 | Listed by Ahsay as affected v10 versions, including v10.3.4.0; the CVE record describes AhsayCBS up to 10.3.4.44 | Hotfix v10.3.4.45, then reboot | Ahsay (October 12, 2026 update), checked |
| AhsayCBS v7, v8, and v9 | Listed by Ahsay as affected v7, v8, and v9 versions, including v9.15.2.59; the CVE record describes AhsayCBS up to 9.15.2.69 | Hotfix v9.15.2.70, then reboot (Ahsay also advised v7 and v8 partners to upgrade to v9.15.0.0 and then apply this hotfix) | Ahsay (October 12, 2026 update), checked |
Patch checklist
- Confirm you run an AhsayCBS edition Ahsay lists as affected: v10, or v7, v8, or v9. Ahsay says earlier patches v10.3.4.0 and v9.15.2.59 did not fully address CVE-2026-105133 and CVE-2026-105134.
- Apply the hotfix Ahsay lists for your line: v10.3.4.45 for affected v10 versions, or v9.15.2.70 for affected v7, v8, and v9 versions. Ahsay says a valid partner portal login is required to download the hotfix. After applying the hotfix, reboot the server, as Ahsay instructs.
- Check the server against the compromise indicators Ahsay lists (unexpected root-level folders, unexpected .jsp files or folders under %CBS%\webapps, unauthorized RPS receivers, or unauthorized Admin accounts). If any of those indicators are present, Ahsay recommends treating the server as compromised and following its full rebuild procedure.
If you can't patch yet
- Ahsay's October 12, 2026, update does not list a workaround. It tells partners to apply the listed hotfix and reboot. Huntress recommended restricting access to the AhsayCBS management interface to trusted addresses or a VPN while a patch was pending, and investigating for signs of compromise. That access restriction is Huntress's guidance, not a substitute Ahsay published for the hotfix.
How to check for compromise
- Look for unexpected folders on the root of hard drives with names such as ahsay_ts, ahsay_t8, ahsay_t9, ahsay_t20, ahsay_t21, srv, user, or opt, which Ahsay says are typically created on the same day.
- In the %CBS%\webapps folder, look for multiple .jsp files with randomly generated names, or folders made of lowercase letters and numbers, which Ahsay lists as an indicator.
- Look for unauthorized RPS receivers, and for unauthorized AhsayCBS user accounts with Admin-type privilege, which Ahsay also lists.
- If any of those indicators are present, Ahsay recommends a full rebuild: reinstall Windows or Linux, install AhsayCBS v9.15.0.0 or v10.3.4.0 and apply hotfix v9.15.2.70 or v10.3.4.45, then restore an Auto Save configuration whose timestamp predates the compromise (Ahsay says to pick a version from at least one day before any suspicious folders or files).
TL;DR: Two AhsayCBS flaws — CVE-2026-105133, an improper-authentication issue, and CVE-2026-105134, an OS command injection issue — have been exploited and chained together. The CVE records, assigned by VulDB and listed in NVD, rate CVE-2026-105134 CVSS 3.1 10.0 (Critical) and CVE-2026-105133 CVSS 3.1 7.3 (High). Huntress says it began seeing exploitation on October 7, 2026, at 23:20:15 UTC, and had seen five organizations targeted as of October 8. Ahsay says it began receiving partner reports of unauthorized access on October 9. CISA added both CVEs to its Known Exploited Vulnerabilities catalog on October 14, 2026, with a due date of October 17, 2026. Ahsay later said earlier patches v10.3.4.0 and v9.15.2.59 did not fully address the flaws. Apply hotfix v10.3.4.45 for affected v10 systems, or v9.15.2.70 for affected v7, v8, and v9 systems, reboot, and check for the compromise indicators Ahsay lists.
What happened
On October 4, 2026, CVE records were published for two vulnerabilities in AhsayCBS, the backup management console in Ahsay Cloud Backup Suite. CVE-2026-105133 is an improper-authentication issue in the checkSysPwd function of the product’s API. CVE-2026-105134 is an OS command injection issue in the Replication Receiver component at /rps/api/json/UpdateReceivers.do. Both records say the attack can be launched remotely, that an exploit is public, and that an earlier patch did not fix the issues properly.
Huntress, in its write-up Threat Actors Exploit Critical AhsayCBS Flaws to Drop Webshells and XMRig Cryptominer, says it began seeing threat actors exploit the two flaws for remote code execution starting October 7, 2026, at 23:20:15 UTC. As of October 8, it had seen five organizations targeted. Huntress says the flaws were chained: CVE-2026-105133 to bypass authentication, then CVE-2026-105134 to run code as NT AUTHORITY/SYSTEM. After exploitation, Huntress observed reconnaissance, Java Server Page webshells, and XMRig cryptominers disguised as Microsoft Edge, among other follow-on activity.
Ahsay’s AhsayCBS Vulnerability Status Update, dated October 13, 2026, says the company began receiving reports from partners on October 9, 2026, of unauthorized access incidents affecting AhsayCBS server environments. On October 9, Ahsay had published a clarification stating that both vulnerabilities had been addressed in AhsayCBS v10.3.4.0, released on August 4, 2026. On October 10, Ahsay issued a critical security alert saying that previous patch v10.3.4.0 did not fully address CVE-2026-105133 and CVE-2026-105134, and telling partners on affected v10 versions to apply hotfix v10.3.4.45 and reboot. An October 12 update repeated that earlier patches v9.15.2.59 and v10.3.4.0 did not fully address the flaws, and added hotfix v9.15.2.70 for affected v7, v8, and v9 versions, again with a reboot. The October 13 status update says those two hotfixes fully address both CVEs.
CISA added CVE-2026-105133 and CVE-2026-105134 to the Known Exploited Vulnerabilities catalog on October 14, 2026, with a due date of October 17, 2026. The KEV entries name the product AhsayCBS, link to Ahsay’s October 12 update, and list knownRansomwareCampaignUse as Unknown. CISA marks CVE-2026-105134 for forensic triage.
Ahsay does not name attackers in its advisories. Huntress describes post-exploitation tools it observed, but does not attribute a named group. We do not add any of that.
Who is exposed
Ahsay’s October 12 update tells partners running affected v10 versions to apply hotfix v10.3.4.45, and partners running affected v7, v8, and v9 versions to apply hotfix v9.15.2.70. Ahsay’s October 13 timeline also advised partners on AhsayCBS v8 and v7 to upgrade to v9.15.0.0 and then apply hotfix v9.15.2.70. The same October 12 notice is explicit that earlier patches v9.15.2.59 and v10.3.4.0 did not fully address the two CVEs.
The CVE records, as listed in NVD, describe AhsayCBS up to 9.15.2.69 / 10.3.4.44, and say upgrading to 9.15.2.70 and 10.3.4.45 addresses the issues. Huntress wrote that versions through 10.3.4 are impacted, including 10.3.4.0, and that it independently verified hotfix 10.3.4.45 mitigates the initial entry point of the attack chain it saw.
Ahsay’s v10.3.6 release notes (November 2, 2026) also list an “Ahsay Security Patchset for CVE-2026-105133 and CVE-2026-105134.” The October advisories that tell partners what to apply still name the v10.3.4.45 and v9.15.2.70 hotfixes.
What to do
- Confirm the AhsayCBS line Ahsay lists, and do not treat the earlier patches as the fix. That includes v10 systems still on v10.3.4.0, and v7, v8, or v9 systems still on v9.15.2.59.
- Apply the hotfix Ahsay lists for your line, then reboot. For affected v10 versions, that is v10.3.4.45. For affected v7, v8, and v9 versions, that is v9.15.2.70. Ahsay says a valid partner portal login is required to download the hotfix, and that the server should be rebooted afterward.
- Check for the compromise indicators Ahsay lists. Those are unexpected folders on the root of hard drives (examples Ahsay gives include ahsay_ts, ahsay_t8, ahsay_t9, ahsay_t20, ahsay_t21, srv, user, and opt); unexpected randomly named
.jspfiles or letter-and-number folders under%CBS%\webapps; unauthorized RPS receivers; and unauthorized Admin-type AhsayCBS accounts. - If any of those indicators are present, follow Ahsay’s rebuild procedure. Ahsay strongly recommends a full rebuild of the backup server: reinstall Windows or Linux, install AhsayCBS v9.15.0.0 or v10.3.4.0 and apply the relevant hotfix (v9.15.2.70 or v10.3.4.45), then restore an Auto Save configuration whose timestamp predates the compromise. Ahsay says to select a version from at least one day before the timestamp of any suspicious folders or files.
Ahsay’s October 12 update does not list a workaround. Huntress recommended restricting management-interface access to trusted addresses or a VPN, and investigating for signs of compromise. Treat that as Huntress’s guidance, not a substitute Ahsay published for the hotfix.
Other alerts are on our security coverage hub.
Updates
- Nov 11, 2026, 8:59 a.m. Manila (UTC+8): Initial report covering Ahsay’s advisories for CVE-2026-105133 and CVE-2026-105134, the v10.3.4.45 and v9.15.2.70 hotfixes, Huntress’s exploitation write-up, and CISA’s October 14, 2026 KEV additions.
Sources & method
- Ahsay, (Update) Critical Security Alert: Immediate Action Required for CVE-2026-105133 and CVE-2026-105134 (October 12, 2026) — https://www.ahsay.com/en/company/announcements/patch-cve-105133-105134-update
- Ahsay, Critical Security Alert: Immediate Action Required for CVE-2026-105133 and CVE-2026-105134 (October 10, 2026) — https://www.ahsay.com/en/company/announcements/patch-cve-105133-105134
- Ahsay, AhsayCBS Vulnerability Status Update (October 13, 2026) — https://www.ahsay.com/en/company/announcements/ahsaycbs-vulnerability-status-update
- Ahsay, Clarification on AhsayCBS v10.3.4.0 vulnerabilities (October 9, 2026) — https://www.ahsay.com/en/company/announcements/clarification-v10.3.4.0-cve
- Ahsay, AhsayCBS (DIY) v10.3.6 Release Notes (November 2, 2026) — https://www.ahsay.com/en/support/help-centre/release-notes/cbs/v10.3.6
- Huntress, Threat Actors Exploit Critical AhsayCBS Flaws to Drop Webshells and XMRig Cryptominer — https://www.huntress.com/blog/ahsaycbs-flaws-exploit
- NVD, CVE-2026-105133 — https://nvd.nist.gov/vuln/detail/CVE-2026-105133
- NVD, CVE-2026-105134 — https://nvd.nist.gov/vuln/detail/CVE-2026-105134
- CVE.org / CVE Program records (CNA: VulDB), CVE-2026-105133 and CVE-2026-105134 — https://www.cve.org/CVERecord?id=CVE-2026-105133 and https://www.cve.org/CVERecord?id=CVE-2026-105134
- CISA Known Exploited Vulnerabilities catalog — https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
Last checked: Nov 11, 2026, 8:57 a.m. Manila (UTC+8). Method: We read Ahsay’s October 9–13, 2026, advisories and the November 2, 2026, v10.3.6 release notes; the NVD and CVE.org records for both CVEs; Huntress’s exploitation write-up; and the CISA KEV JSON feed. Both CVEs are listed in catalog version 2026.11.10, dateAdded 2026-10-14, dueDate 2026-10-17, as of Nov 11, 2026, 8:57 a.m. Manila (UTC+8). CVSS figures are the VulDB scores listed in those CVE/NVD records (no separate NIST base score was published). We use the hotfix versions Ahsay published, and we do not treat v10.3.4.0 or v9.15.2.59 as the fix. Thumbnail is a reuse-licensed image, credited with its license under the picture. No affiliate links. How we work.
Spotted an error? See our corrections policy and tell us.



