CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

AhsayCBS, Replication Receiver /rps/api/json/UpdateReceivers.do unauthenticated code execution as SYSTEM (VulDB CVSS 4.0 10.0), exploited from 2026-10-07; 10.3.4 also affected per Huntress

cve · CVE-2026-105134

Coverage
1
first 2026-10-10 → last 2026-11-10
Latest activity
2026-11-10
Ahsay admits its earlier AhsayCBS patches were incomplete; the hotfixes are partner-only and CISA lists both…
Peak priority
high
1 high
Targets
technology
sectors: technology
Sources cited
9
7 hosts

Action items (2)

Do-now tasks recorded on the entries about CVE-2026-105134, newest first. Check the date before acting on an older one.

  • Find every AhsayCBS server your organisation or your managed-service suppliers run, including those already on v10.3.4.0 or v9.15.2.59, and apply the hotfix v10.3.4.45 (v10) or v9.15.2.70 (v7, v8, v9) now, then reboot it; the hotfixes sit behind Ahsay's partner portal, so ask the integrator or Ahsay for the build, and until it is applied keep the management web interface behind a VPN or an allowlist of trusted addresses.
    2026-10-10CVE-2026-105133 +1
  • Compromise-check every AhsayCBS server that was internet-reachable since 2026-10-04 against the indicators Huntress and Bitdefender publish, an OpenSSH service nobody installed included, and against Horizon3's server-side checks (new .jsp files in served application directories, replication receivers created outside a change window, unexpected system administrator accounts), and re-image any host with a confirmed compromise from a trusted backup, because the hotfix does not remove a webshell or a persistence mechanism that is already there; a missing webshell file does not show a clean host because one family deletes itself, and the credentials stored on or reachable from the server, those held in AhsayCBS and in other backup software on the same network included, must be rotated.
    2026-10-10CVE-2026-105133 +1

Defender insights

What each entry about CVE-2026-105134 tells a defender to do, newest first.

2026-10-10HIGHexploitedAhsay admits its earlier AhsayCBS patches were incomplete; the hotfixes are partner-only and CISA lists both flaws as exploited

Exposure · triage · detection

Story timeline

  1. 2026-10-10CVE-2026-105133 / CVE-2026-105134, AhsayCBS backup management console: an unauthenticated authentication-bypass and code-execution chain exploited since 7 October to drop webshells and a cryptominer; Ahsay says its earlier patches were incomplete and ships hotfixes 10.3.4.45 and 9.15.2.70 through its partner portal
    trending-vulnerabilitiesAhsay admits its earlier AhsayCBS patches were incomplete; the hotfixes are partner-only and CISA lists both flaws as exploited
ATT&CK techniques (30 across 11 tactics)

30 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • Resource DevelopmentStage Capabilities: Upload Malware
  • Initial AccessExternal Remote Services · Exploit Public-Facing Application
  • ExecutionScheduled Task/Job: Scheduled Task · Command and Scripting Interpreter: PowerShell · Command and Scripting Interpreter: Windows Command Shell · Command and Scripting Interpreter: Python · System Services: Service Execution
  • PersistenceScheduled Task/Job: Scheduled Task · External Remote Services · Create Account: Local Account · Server Software Component: Web Shell · Create or Modify System Process: Windows Service · Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder
  • Privilege EscalationScheduled Task/Job: Scheduled Task · Create or Modify System Process: Windows Service · Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder
  • StealthObfuscated Files or Information · Obfuscated Files or Information: Steganography · Masquerading: Masquerade Task or Service · Masquerading: Match Legitimate Resource Name or Location · Execution Guardrails: Environmental Keying · Hide Artifacts · Reflective Code Loading
  • Defense ImpairmentDisable or Modify Tools
  • Credential AccessUnsecured Credentials · Credentials from Password Stores
  • DiscoveryProcess Discovery · System Time Discovery
  • Command and ControlApplication Layer Protocol: Web Protocols · Ingress Tool Transfer · Remote Access Tools · Non-Standard Port · Protocol Tunneling
  • ImpactResource Hijacking: Compute Hijacking

Resource Development TA0042

T1608.001Stage Capabilities: Upload Malware×1

Adversaries may upload malware to third-party or adversary controlled infrastructure to make it accessible during targeting. Malicious software can include payloads, droppers, post-compromise tools, backdoors, and a variety of other malicious content. Adversaries may upload malware to support their operations, such as making a payload available to a victim network to enable Ingress Tool Transfer by placing it on an Internet accessible web server.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

Initial Access TA0001

T1133External Remote Services×1

Adversaries may leverage external-facing remote services to initially access and/or persist within a network. Remote services such as VPNs, Citrix, and other access mechanisms allow users to connect to internal enterprise network resources from external locations. There are often remote service gateways that manage connections and credential authentication for these services. Services such as Windows Remote Management and VNC can also be used externally.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1190Exploit Public-Facing Application×1

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

Execution TA0002

T1053.005Scheduled Task/Job: Scheduled Task×1

Adversaries may abuse the Windows Task Scheduler to perform task scheduling for initial or recurring execution of malicious code. There are multiple ways to access the Task Scheduler in Windows. The schtasks utility can be run directly on the command line, or the Task Scheduler can be opened through the GUI within the Administrator Tools section of the Control Panel. In some cases, adversaries have used a .NET wrapper for the Windows Task Scheduler, and alternatively, adversaries have used the Windows netapi32 library and Windows Management Instrumentation (WMI) to create a scheduled task. Adversaries may also utilize the Powershell Cmdlet `Invoke-CimMethod`, which leverages WMI class `PS_ScheduledTask` to create a scheduled task via an XML path.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1059.001Command and Scripting Interpreter: PowerShell×1

Adversaries may abuse PowerShell commands and scripts for execution. PowerShell is a powerful interactive command-line interface and scripting environment included in the Windows operating system. PowerShell can also be installed on Linux and macOS. Adversaries can use PowerShell to perform a number of actions, including discovery of information and execution of code. Examples include the <code>Start-Process</code> cmdlet which can be used to run an executable and the <code>Invoke-Command</code> cmdlet which runs a command locally or on a remote computer (though administrator permissions are required to use PowerShell to connect to remote systems).

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1059.003Command and Scripting Interpreter: Windows Command Shell×1

Adversaries may abuse the Windows command shell for execution. The Windows command shell (cmd) is the primary command prompt on Windows systems. The Windows command prompt can be used to control almost any aspect of a system, with various permission levels required for different subsets of commands. The command prompt can be invoked remotely via Remote Services such as SSH.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1059.006Command and Scripting Interpreter: Python×1

Adversaries may abuse Python commands and scripts for execution. Python is a very popular scripting/programming language, with capabilities to perform many functions. Python can be executed interactively from the command-line (via the <code>python.exe</code> interpreter) or via scripts (.py) that can be written and distributed to different systems. Python code can also be compiled into binary executables.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1569.002System Services: Service Execution×1

Adversaries may abuse the Windows service control manager to execute malicious commands or payloads. The Windows service control manager (<code>services.exe</code>) is an interface to manage and manipulate services. The service control manager is accessible to users via GUI components as well as system utilities such as <code>sc.exe</code> and Net.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

Persistence TA0003

T1053.005Scheduled Task/Job: Scheduled Task×1

Adversaries may abuse the Windows Task Scheduler to perform task scheduling for initial or recurring execution of malicious code. There are multiple ways to access the Task Scheduler in Windows. The schtasks utility can be run directly on the command line, or the Task Scheduler can be opened through the GUI within the Administrator Tools section of the Control Panel. In some cases, adversaries have used a .NET wrapper for the Windows Task Scheduler, and alternatively, adversaries have used the Windows netapi32 library and Windows Management Instrumentation (WMI) to create a scheduled task. Adversaries may also utilize the Powershell Cmdlet `Invoke-CimMethod`, which leverages WMI class `PS_ScheduledTask` to create a scheduled task via an XML path.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1133External Remote Services×1

Adversaries may leverage external-facing remote services to initially access and/or persist within a network. Remote services such as VPNs, Citrix, and other access mechanisms allow users to connect to internal enterprise network resources from external locations. There are often remote service gateways that manage connections and credential authentication for these services. Services such as Windows Remote Management and VNC can also be used externally.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1136.001Create Account: Local Account×1

Adversaries may create a local account to maintain access to victim systems. Local accounts are those configured by an organization for use by users, remote support, services, or for administration on a single system or service.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1505.003Server Software Component: Web Shell×1

Adversaries may backdoor web servers with web shells to establish persistent access to systems. A Web shell is a Web script that is placed on an openly accessible Web server to allow an adversary to access the Web server as a gateway into a network. A Web shell may provide a set of functions to execute or a command-line interface on the system that hosts the Web server.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1543.003Create or Modify System Process: Windows Service×1

Adversaries may create or modify Windows services to repeatedly execute malicious payloads as part of persistence. When Windows boots up, it starts programs or applications called services that perform background system functions. Windows service configuration information, including the file path to the service's executable or recovery programs/commands, is stored in the Windows Registry.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1547.001Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder×1

Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. These programs will be executed under the context of the user and will have the account's associated permissions level.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

Privilege Escalation TA0004

T1053.005Scheduled Task/Job: Scheduled Task×1

Adversaries may abuse the Windows Task Scheduler to perform task scheduling for initial or recurring execution of malicious code. There are multiple ways to access the Task Scheduler in Windows. The schtasks utility can be run directly on the command line, or the Task Scheduler can be opened through the GUI within the Administrator Tools section of the Control Panel. In some cases, adversaries have used a .NET wrapper for the Windows Task Scheduler, and alternatively, adversaries have used the Windows netapi32 library and Windows Management Instrumentation (WMI) to create a scheduled task. Adversaries may also utilize the Powershell Cmdlet `Invoke-CimMethod`, which leverages WMI class `PS_ScheduledTask` to create a scheduled task via an XML path.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1543.003Create or Modify System Process: Windows Service×1

Adversaries may create or modify Windows services to repeatedly execute malicious payloads as part of persistence. When Windows boots up, it starts programs or applications called services that perform background system functions. Windows service configuration information, including the file path to the service's executable or recovery programs/commands, is stored in the Windows Registry.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1547.001Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder×1

Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. These programs will be executed under the context of the user and will have the account's associated permissions level.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

Stealth TA0005

T1027Obfuscated Files or Information×1

Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit. This is common behavior that can be used across different platforms and the network to evade defenses.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1027.003Obfuscated Files or Information: Steganography×1

Adversaries may use steganography techniques in order to prevent the detection of hidden information. Steganographic techniques can be used to hide data in digital media such as images, audio tracks, video clips, or text files.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1036.004Masquerading: Masquerade Task or Service×1

Adversaries may attempt to manipulate the name of a task or service to make it appear legitimate or benign. Tasks/services executed by the Task Scheduler or systemd will typically be given a name and/or description. Windows services will have a service name as well as a display name. Many benign tasks and services exist that have commonly associated names. Adversaries may give tasks or services names that are similar or identical to those of legitimate ones.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1036.005Masquerading: Match Legitimate Resource Name or Location×1

Adversaries may match or approximate the name or location of legitimate files, Registry keys, or other resources when naming/placing them. This is done for the sake of evading defenses and observation.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1480.001Execution Guardrails: Environmental Keying×1

Adversaries may environmentally key payloads or other features of malware to evade defenses and constraint execution to a specific target environment. Environmental keying uses cryptography to constrain execution or actions based on adversary supplied environment specific conditions that are expected to be present on the target. Environmental keying is an implementation of Execution Guardrails that utilizes cryptographic techniques for deriving encryption/decryption keys from specific types of values in a given computing environment.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1564Hide Artifacts×1

Adversaries may attempt to hide artifacts associated with their behaviors to evade detection. Operating systems may have features to hide various artifacts, such as important system files and administrative task execution, to avoid disrupting user work environments and prevent users from changing files or features on the system. Adversaries may abuse these features to hide artifacts such as files, directories, user accounts, or other system activity to evade detection.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1620Reflective Code Loading×1

Adversaries may reflectively load code into a process in order to conceal the execution of malicious payloads. Reflective loading involves allocating then executing payloads directly within the memory of the process, vice creating a thread or process backed by a file path on disk (e.g., Shared Modules).

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

Defense Impairment TA0112

T1685Disable or Modify Tools×1

Adversaries may disable, degrade, or tamper with security tools or applications (e.g., endpoint detection and response (EDR) tools, intrusion detection systems (IDS), antivirus, logging agents, sensors, etc.) to impair or reduce visibility of defensive capabilities. This may include stopping specific services, killing processes, modifying or deleting tool configuration files and Registry keys, or preventing tools from updating. This may also include impairing defenses more broadly by disrupting preventative, detection, and response mechanisms across host, network, and cloud environments.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

Credential Access TA0006

T1552Unsecured Credentials×1

Adversaries may search compromised systems to find and obtain insecurely stored credentials. These credentials can be stored and/or misplaced in many locations on a system, including plaintext files (e.g. Shell History), operating system or application-specific repositories (e.g. Credentials in Registry), or other specialized files/artifacts (e.g. Private Keys).

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1555Credentials from Password Stores×1

Adversaries may search for common password storage locations to obtain user credentials. Passwords are stored in several places on a system, depending on the operating system or application holding the credentials. There are also specific applications and services that store passwords to make them easier for users to manage and maintain, such as password managers and cloud secrets vaults. Once credentials are obtained, they can be used to perform lateral movement and access restricted information.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

Discovery TA0007

T1057Process Discovery×1

Adversaries may attempt to get information about running processes on a system. Information obtained could be used to gain an understanding of common software/applications running on systems within the network. Administrator or otherwise elevated access may provide better process details. Adversaries may use the information from Process Discovery during automated discovery to shape follow-on behaviors, including whether or not the adversary fully infects the target and/or attempts specific actions.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1124System Time Discovery×1

An adversary may gather the system time and/or time zone settings from a local or remote system. The system time is set and stored by services, such as the Windows Time Service on Windows or <code>systemsetup</code> on macOS. These time settings may also be synchronized between systems and services in an enterprise network, typically accomplished with a network time server within a domain.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

Command and Control TA0011

T1071.001Application Layer Protocol: Web Protocols×1

Adversaries may communicate using application layer protocols associated with web traffic to avoid detection/network filtering by blending in with existing traffic. Commands to the remote system, and often the results of those commands, will be embedded within the protocol traffic between the client and server.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1105Ingress Tool Transfer×1

Adversaries may transfer tools or other files from an external system into a compromised environment. Tools or files may be copied from an external adversary-controlled system to the victim network through the command and control channel or through alternate protocols such as ftp. Once present, adversaries may also transfer/spread tools between victim devices within a compromised environment (i.e. Lateral Tool Transfer).

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1219Remote Access Tools×1

An adversary may use legitimate remote access tools to establish an interactive command and control channel within a network. Remote access tools create a session between two trusted hosts through a graphical interface, a command line interaction, a protocol tunnel via development or management software, or hardware-level access such as KVM (Keyboard, Video, Mouse) over IP solutions. Desktop support software (usually graphical interface) and remote management software (typically command line interface) allow a user to control a computer remotely as if they are a local user inheriting the user or software permissions. This software is commonly used for troubleshooting, software installation, and system management. Adversaries may similarly abuse response features included in EDR and other defensive tools that enable remote access.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1571Non-Standard Port×1

Adversaries may communicate using a protocol and port pairing that are typically not associated (for example, HTTPS over port 8088 or port 587 as opposed to the traditional port 443). Adversaries may make changes to the standard port used by a protocol to bypass filtering or muddle analysis/parsing of network data.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

T1572Protocol Tunneling×1

Adversaries may tunnel network communications to and from a victim system within a separate protocol to avoid detection/network filtering and/or enable access to otherwise unreachable systems. Tunneling involves explicitly encapsulating a protocol within another. This behavior may conceal malicious traffic by blending in with existing traffic and/or provide an outer layer of encryption (similar to a VPN). Tunneling could also enable routing of network packets that would otherwise not reach their intended destination, such as SMB, RDP, or other traffic that would be filtered by network appliances or not routed over the Internet.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

Impact TA0040

T1496.001Resource Hijacking: Compute Hijacking×1

Adversaries may leverage the compute resources of co-opted systems to complete resource-intensive tasks, which may impact system and/or hosted service availability.

Evidence: 2026-10-10/ahsaycbs-cve-2026-105133-105134-exploited-webshells-xmrig · ATT&CK page ↗

Entries about AhsayCBS, Replication Receiver /rps/api/json/UpdateReceivers.do unauthenticated code execution as SYSTEM (VulDB CVSS 4.0 10.0), exploited from 2026-10-07; 10.3.4 also affected per Huntress (1)

2026-10-10 · view entry permalink →

HIGHCVE-2026-105133 +1exploitedupdatedNATOB1

CVE-2026-105133 / CVE-2026-105134, AhsayCBS backup management console: an unauthenticated authentication-bypass and code-execution chain exploited since 7 October to drop webshells and a cryptominer; Ahsay says its earlier patches were incomplete and ships hotfixes 10.3.4.45 and 9.15.2.70 through its partner portal

Huntress reports that from 2026-10-07 23:20 UTC attackers exploited two flaws in AhsayCBS, the management console of Ahsay's backup software that managed service providers and system integrators mainly use, to gain unauthenticated remote code execution and deploy webshells on exposed servers (Huntress, 2026-10-08). CVE-2026-105133, an improper-authentication flaw in the checkSysPwd function of the API, is used first to bypass authentication; CVE-2026-105134, in the /rps/api/json/UpdateReceivers.do endpoint of the Replication Receiver component, then gives code execution as NT AUTHORITY\SYSTEM, after which the attacker configured a malicious receiver and dropped a JSP webshell into the directory the application serves (Huntress, 2026-10-08). BleepingComputer reports that the activity targeted at least five organizations on 7 October and that CVE-2026-105133 has a public exploit (BleepingComputer, 2026-10-09).

Follow-on activity, per Huntress: commands spawned by the AhsayCBS service process fetch payloads over HTTP from cloud object storage into a Temp folder with curl and certutil; an XMRig Monero miner renamed to look like a Microsoft Edge binary runs as SYSTEM through a service that mimics the Edge updater and a renamed copy of the NSSM service manager; and a PowerShell script hides the miner while Task Manager is open (Huntress, 2026-10-08). The earlier patches did not close the flaws: public records had listed AhsayCBS up to 10.3.2 as affected (SecurityWeek, 2026-10-09), Huntress found on 2026-10-08 that 10.3.4 is also affected (Huntress, 2026-10-08), and Ahsay's release notes for 10.3.4 list no security fix (Ahsay, 2026-08-05).

Triage: AhsayCBS legitimately spawns its own startup and maintenance commands, so a child process alone is weak; the discriminators Huntress gives are a child of the service that downloads files into a Temp folder, and an Edge-named binary run as SYSTEM from a Temp folder under a service that mimics the Edge updater (Huntress, 2026-10-08).

Starting 2026-10-07 23:20:15 UTC, Huntress observed threat actors exploiting the vulnerabilities to gain unauthenticated remote code execution and deploy webshells on exposed systems.

After further investigation, Huntress has determined that Ahsay 10.3.4 is also affected by these vulnerabilities.

Huntress 2026-10-08

The malicious activity was observed on October 7, and targeted at least five organizations.

BleepingComputer 2026-10-09

did not fully address the following security vulnerabilities

Ahsay

Huntress has independently verified that the AhsayCBS 10.3.4.45 hotfix mitigates the initial entry point of this attack chain

Huntress 2026-10-08

Bitdefender MDR investigations and the KEV listing both confirm exploitation.

Bitdefender 2026-10-15

based on evidence of active exploitation

CISA 2026-10-14

and the credential check is never reached

On Linux it runs as root.

Horizon3.ai 2026-10-14

the shell can delete itself after use, so not finding the file on disk does not prove it was never present

Huntress 2026-10-08
Updaterun 2026-10-16T0256Z-inteltitleheadlinesummaryprioritytagstechniquescvessourcesevidenceverificationsourcing_noteconfidenceclassificationactionsbody

Ahsay now says its previous patches v9.15.2.59 and v10.3.4.0 "did not fully address" the two flaws, and tells partners to apply the AhsayCBS v10.3.4.45 hotfix on v10 and the v9.15.2.70 hotfix on v7, v8 and v9, both from the partner portal (a valid partner login is required), then to reboot the server (Ahsay, 2026-10-12). The announcement is dated 2026-10-12; Huntress, in an update of the same day to its report, dates the hotfix release to that day and says it independently verified that the v10.3.4.45 hotfix mitigates the initial entry point of the chain, which was still open on earlier v10 versions (Huntress, 2026-10-08).

CISA added both flaws to its Known Exploited Vulnerabilities catalog on 2026-10-14 "based on evidence of active exploitation" (CISA, 2026-10-14). Bitdefender MDR reports three intrusions through the chain, the first two beginning around 7 to 8 October and a third identified on 14 October; in the first, attackers validated access through JSP webshells, staged PowerShell payloads, tried to stage payloads as command files in C:\Users\Public and tried to establish persistence; in the second they deployed JSP files, tried the same command-file staging, searched for stored credentials, elevated an account to SYSTEM and used obfuscated PowerShell to install and configure OpenSSH, which gives a way back that does not depend on the vulnerable web service, so patching alone does not end the incident; across its incidents the follow-on PowerShell scripts were staged on a subdomain of a public static-site hosting service; it attributes the activity to no named actor, and notes that the file names, tools and binaries differed from one incident to the next, so the dependable signal is how the server behaves after the exploit fires (Bitdefender, 2026-10-15).

Improvementrun 2026-10-18T0256Z-intelsourcesevidenceactionsbody

Horizon3.ai published a source-level analysis of both flaws on 2026-10-14, working from the Linux installer, and says its proof of concept for the chain, from authentication bypass to a webshell, is on its GitHub (Horizon3.ai, 2026-10-14). For CVE-2026-105133, every action of the JSON API extends a base class whose administrator password check is skipped when the request body carries a FromServlet flag that the caller sets, so the JSON API is reachable without credentials, and the AddSysUser action, which creates a system administrator, never consults the caller (Horizon3.ai, 2026-10-14). For CVE-2026-105134, an authentication-bypassed call creates a replication receiver whose home directory the attacker chooses; the system-folder denylist that screens that directory at creation is not applied to the upload path later built from two attacker-supplied headers, in which only the percent and colon characters are escaped, so a traversal sequence walks the write location into a served web application, and one upload of a .jsp file then runs as LocalSystem on Windows and as root on Linux (Horizon3.ai, 2026-10-14). Horizon3 says Ahsay released its hotfixes on 12 October 2026 (Horizon3.ai, 2026-10-14).

Updaterun 2026-11-10T0255Z-inteltechniquessourcesevidencesourcing_noteactionsbody

Huntress's follow-up covers an organisation whose AhsayCBS servers were exploited between 8 and 11 October 2026, before Ahsay's hotfixes; Huntress verified that 10.3.4.45 blocks the entry point it saw and ties the intrusion to the first campaign by webshell location, an exploit source address and matching files (Huntress, 2026-11-09). The operator planted five JSP webshell families under the console's web application directories (Huntress, 2026-11-09); Huntress reads the Linux-style copies, in directories such as /opt, /usr/local and /home, as showing that the exploit simply tried every likely location (Huntress, 2026-11-09). One family hides an AES-encrypted Java class in the least-significant bits of an uploaded PNG's pixels and runs it in memory, so no command parameter appears in access logs; another is a signed-API shell with command execution and chunked upload and download of up to 4 GB per file, a ready exfiltration channel on a backup host; a third can delete itself and any path it is given, so a missing file does not prove it was never there (Huntress, 2026-11-09).

Huntress also found a second XMRig miner kept alive by a SYSTEM scheduled task with a backdated start time that runs every minute, an embedded Python distribution under the SYSTEM profile started from a Run key whose wrapper only runs if a marker file named for the SHA-256 of the host's MachineGuid exists and which then loads a DLL whose strings are consistent with DNS-over-HTTPS lookups, the tunnelling tools gost and chisel, the remote access tools AnyDesk, Atera and Splashtop, a rogue local account, a Mimikatz package and Microsoft Defender exclusions that include the AhsayCBS service process (Huntress, 2026-11-09). On a Veeam server in the same environment it saw a command consistent with NetExec's Veeam credential-theft module, a PowerShell script launched through WMI that queried the VeeamBackup database for stored credentials and decrypted them; it cannot say how many credentials were retrieved, has not identified the implant family and cannot say what, if anything, was taken through the webshell's download action (Huntress, 2026-11-09). For any server exposed before the hotfix, Huntress recommends a full re-image from a trusted backup and rotating the credentials stored on or reachable from the server, including those saved in AhsayCBS and in any backup software on the same network (Huntress, 2026-11-09).

vulnerability10 Oct 03:51Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1

Source distribution

  • ahsay.com2 (22%)
  • huntress.com2 (22%)
  • bitdefender.com1 (11%)
  • bleepingcomputer.com1 (11%)
  • cisa.gov1 (11%)
  • horizon3.ai1 (11%)
  • securityweek.com1 (11%)