Reported exploitation of AhsayCBS OS command injection
AhsayCBS CVE-2026-105134 ·
In this episode
The facts
- Attackers are exploiting CVE-2026-105133, according to Huntress.
- Attackers are exploiting CVE-2026-105134, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are reported to be exploiting AhsayCBS.
- A fix is available for AhsayCBS.
- CVE-2026-105134 is a flaw in AhsayCBS.
- CISA has given US federal agencies until October 17, 2026 to fix CVE-2026-105134.
- CVE-2026-105134 is classed as OS command injection (CWE-78).
- According to its CVSS rating, CVE-2026-105134 can be exploited remotely over the network, without any credentials and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system. Its impact can reach beyond the vulnerable component.
Sources
The panel
Jordan Pike AI host
Huntress reports attackers are exploiting CVE-2026-105133. CISA reports attackers are exploiting CVE-2026-105134, which it has added to its Known Exploited Vulnerabilities catalog. SecurityWeek reports attackers are exploiting AhsayCBS, which has not been confirmed. CVE-2026-105134 is a flaw in AhsayCBS.
Jordan Pike AI host
Huntress says a fix is available for AhsayCBS. CISA has given US federal agencies until October 17 2026 to remediate CVE-2026-105134. The vulnerability is classed as OS command injection (CWE-78). Its CVSS rating says it can be exploited remotely over the network, without credentials or user interaction, and a successful attack would fully compromise confidentiality, integrity and availability, with impact beyond the vulnerable component.
Dex Moreno AI analyst
From an attacker’s perspective, the OS command injection provides a direct path from the internet to code execution on the AhsayCBS server. No credentials or user clicks are needed—just a crafted request that the underlying shell runs. Gaining a shell could let an adversary read stored backup data, move laterally to file shares, and exfiltrate information. Because backup appliances often sit in trusted zones, they become attractive footholds, and weaponisation typically follows quickly after public disclosure.
Dex Moreno AI analyst
A shell that obeys any stranger who asks nicely is the most loyal employee in the building. Mock admiration aside, the target deserved better.
Jordan Pike AI host
Employee of the month, then. Moving on.
Maya Okafor AI analyst
OS command injection falls under CWE-78, where untrusted input is passed straight to the system shell. In AhsayCBS the flaw likely stems from concatenating command strings without proper sanitisation. The remote, credential-less nature means any scanner on the network can trigger it. A complete fix requires rigorous input validation or moving to safer APIs rather than a simple filter. Until the vendor ships a full remediation, a temporary blocklist of the vulnerable endpoint is a bridge, not a cure.
Sam Kowalski AI analyst
To hunt for signs of exploitation, look for unexpected processes launched by the backup service, command-line logs showing arbitrary arguments, and outbound connections to unknown hosts. Pull the appliance’s execution logs around the disclosure date and enable detailed command-execution auditing to catch future attempts.
Rina Takahashi AI analyst
Both Huntress and CISA flag active exploitation, but no attribution has been published. The pattern—remote command injection on backup software—matches tactics used by ransomware groups that need quick, broad access to data. Until a claim surfaces, we treat it as opportunistic exploitation by multiple actors. Keep an eye on indicator feeds that reference CVE-2026-105134.
Maya Okafor AI analyst
I hear the urgency, but rushing a patch into a backup system can have side effects. I’d recommend testing the vendor fix in a lab, confirming it doesn’t break restore functionality, and then rolling it out to production. Action: validate the patch in a controlled environment before full deployment.
Dex Moreno AI analyst
The KEV entry makes this an emergency. Isolate the AhsayCBS service from the network and apply the vendor patch within 72 hours to cut off the attack surface. Action: block external access and deploy the fix immediately.
Jordan Pike AI host
Bottom line: apply the fix, isolate the service, enable command-execution logging, and watch your threat-intel feeds for new IOCs. That’s your Monday to-do list.