Ahsay AhsayCBS Command Injection (CVE-2026-105134)
Detects exploitation of CVE-2026-105134, a command injection vulnerability in Ahsay AhsayCBS (Cloud Backup Suite) backup server. The flaw (CWE-77/CWE-78) allows an attacker to inject OS commands through unsanitized input processed by AhsayCBS web/management components, resulting in arbitrary command execution in the context of the AhsayCBS service account. The vulnerability is listed in CISA KEV (known exploited) and is subject to CISA BOD 26-04 remediation prioritization. This detection surfaces anomalous child-process spawning from AhsayCBS/Java processes, suspicious web-access patterns to AhsayCBS management endpoints, and shell/command-interpreter execution originating from the backup server tier.
Vulnerability Intelligence
KEV — Known ExploitedAffected Software
- Vendor
- Ahsay
- Product
- AhsayCBS
Timeline
- Disclosed
- October 14, 2026
References & Proof of Concept
- https://www.ahsay.com/en/company/announcements/patch-cve-105133-105134-update
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2026-105134
CVSS
What is CVE-2026-105134 Ahsay AhsayCBS Command Injection (CVE-2026-105134)?
Ahsay AhsayCBS Command Injection (CVE-2026-105134) (CVE-2026-105134) maps to the Initial Access and Execution tactics — the adversary is trying to get into your network in MITRE ATT&CK.
This page provides production-ready detection logic for Ahsay AhsayCBS Command Injection (CVE-2026-105134), covering the data sources and telemetry it touches: Microsoft Defender for Endpoint, DeviceProcessEvents. The queries below are rated critical severity at high confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.
MITRE ATT&CK
- Tactic
- Initial Access Execution
let AhsayParents = dynamic(["java.exe","javaw.exe","AhsayCBS.exe","httpd.exe","tomcat.exe","catalina.exe"]);
let SuspiciousChildren = dynamic(["cmd.exe","powershell.exe","pwsh.exe","bash.exe","sh.exe","wscript.exe","cscript.exe","certutil.exe","bitsadmin.exe","curl.exe","wget.exe","whoami.exe","net.exe","net1.exe","nltest.exe"]);
DeviceProcessEvents
| where InitiatingProcessFileName in~ (AhsayParents) or InitiatingProcessFolderPath has_any ("AhsayCBS","Ahsay\\")
| where FileName in~ (SuspiciousChildren)
| project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, InitiatingProcessFolderPath, InitiatingProcessCommandLine, FileName, ProcessCommandLine, ReportId
| sort by Timestamp desc Flags command-interpreter and recon/download utilities spawned by AhsayCBS Java/web processes, indicating command-injection exploitation of CVE-2026-105134.
Data Sources
Required Tables
False Positives
- Legitimate AhsayCBS maintenance or backup pre/post-command scripts configured by administrators that invoke cmd.exe or PowerShell.
- Security or inventory agents that spawn child processes under the Java runtime during scheduled scans.
- Administrator-initiated troubleshooting sessions on the backup server using PowerShell or cmd.
Sigma rule & cross-platform mapping
The detection logic for Ahsay AhsayCBS Command Injection (CVE-2026-105134) (CVE-2026-105134) above is provided in a vendor-neutral
form so you can deploy it on any SIEM. The same logic is shipped here as native
KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the
following logsource:
logsource:
category: process_creation
product: windows Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for CVE-2026-105134
References (4)
- https://www.ahsay.com/en/company/announcements/patch-cve-105133-105134-update
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2026-105134
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1 AhsayCBS-style command injection via Java child shell (Windows)
Expected signal: Process creation event with ParentImage containing java and child cmd.exe executing whoami/hostname/net user.
- Test 2 Injected download via certutil from backup-server shell (Windows)
Expected signal: Process creation of certutil.exe with -urlcache download arguments under a cmd.exe child.
- Test 3 AhsayCBS command injection via shell on Linux
Expected signal: Linux process execution event showing java parent spawning /bin/sh running id/uname/whoami.
Response Playbook
Triage
- Confirm the affected host runs Ahsay AhsayCBS and determine the running version; compare against the Ahsay patch advisory for CVE-2026-105133/105134 to establish exposure.
- Review the parent/child process chain: confirm the shell or utility was spawned directly by the AhsayCBS Java/Tomcat process rather than by an administrator session or legitimate backup hook.
- Pull the full command line of the child process and any downstream processes; look for encoded PowerShell, certutil/bitsadmin downloads, reconnaissance (whoami, net, nltest), or reverse-shell indicators.
- Correlate the process event time with AhsayCBS web/management access logs to identify the source IP and request that triggered the injection.
Containment
- Isolate the AhsayCBS host from the network (EDR network containment or VLAN quarantine) to halt command execution and lateral movement.
- Block the identified attacker source IP(s) at the perimeter and disable external exposure of the AhsayCBS management interface until patched.
- Suspend or reset the AhsayCBS service account credentials and any credentials accessible from the backup server.
Evidence Collection
- Capture full process creation telemetry (parent/child, command lines, hashes) and the AhsayCBS application/web access logs covering the exploitation window.
- Preserve a forensic disk and memory image of the AhsayCBS host before remediation, including the AhsayCBS install directory, logs, and any dropped files in temp/web directories.
Escalation Criteria
- ! Escalate to incident response immediately if the spawned process executed downloads, created accounts, modified backup data, or established outbound C2 connections.
- ! Escalate to the data-protection/crisis team if evidence shows access to or tampering with backup repositories, given the sensitivity of backup data on AhsayCBS.
Investigation Guide
Forensic Artifacts
- >
AhsayCBS web/management access logs showing the malicious request parameters. - >
Process creation events linking the Java/Tomcat parent to shell/recon child processes. - >
Newly created or modified files in the AhsayCBS install and web/temp directories (potential web shells or dropped tools).
Tuning Guidance
Baseline legitimate AhsayCBS administrator backup command hooks (pre/post-backup scripts) and exclude their specific command-line patterns and invoking accounts. Restrict the detection to hosts confirmed to run AhsayCBS to reduce noise. If an EDR or management agent legitimately spawns shells under the Java runtime, exclude by signed image path rather than by process name alone.
Hunting Queries
Hunts for AhsayCBS-parented processes executing encoded PowerShell, download utilities, or reconnaissance commands indicative of post-exploitation.
DeviceProcessEvents | where InitiatingProcessFileName in~ ("java.exe","javaw.exe") and InitiatingProcessFolderPath has "Ahsay" | where ProcessCommandLine has_any ("Invoke-","-enc","certutil","bitsadmin","whoami","nltest","net user") | project Timestamp, DeviceName, FileName, ProcessCommandLine index=endpoint sourcetype=Sysmon EventCode=1 (ParentImage="*java*" OR ParentImage="*Ahsay*") (CommandLine="*-enc*" OR CommandLine="*certutil*" OR CommandLine="*bitsadmin*" OR CommandLine="*whoami*" OR CommandLine="*net user*") | table _time host ParentImage Image CommandLine Atomic Red Team Tests
Simulates command injection by having a Java process spawn cmd.exe to run reconnaissance, mimicking CVE-2026-105134 exploitation telemetry.
Command
java -version 2>&1 | Out-Null; Start-Process -FilePath "$env:ComSpec" -ArgumentList '/c whoami & hostname & net user' -NoNewWindow -Wait Cleanup
Remove-Variable -Name ComSpec -ErrorAction SilentlyContinue; echo 'no persistent artifacts created' Expected Telemetry
Process creation event with ParentImage containing java and child cmd.exe executing whoami/hostname/net user.
Expected Detection
KQL/SPL/EDL rules fire on java.exe spawning cmd.exe with recon command line.
Emulates a post-injection payload download using certutil launched from a shell under a Java-style parent.
Command
& "$env:ComSpec" /c "certutil.exe -urlcache -split -f http://127.0.0.1/test.txt %TEMP%\ahsay_test.txt" Cleanup
Remove-Item -Path "$env:TEMP\ahsay_test.txt" -ErrorAction SilentlyContinue Expected Telemetry
Process creation of certutil.exe with -urlcache download arguments under a cmd.exe child.
Expected Detection
Detection fires on certutil download utility invoked in the AhsayCBS process chain.
Simulates command injection on a Linux AhsayCBS host where the Java process spawns a shell running reconnaissance, matching CVE-2026-105134 behavior.
Command
java -version 2>/dev/null; /bin/sh -c 'id; uname -a; whoami > /tmp/ahsay_cve_test.txt' Cleanup
rm -f /tmp/ahsay_cve_test.txt Expected Telemetry
Linux process execution event showing java parent spawning /bin/sh running id/uname/whoami.
Expected Detection
Elastic EQL / Chronicle rule fires on Java parent spawning sh with recon commands.