CVE-2026-105134: Ahsay AhsayCBS Command Injection Vulnerability
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
A flaw has been found in Ahsay AhsayCBS up to 9.15.2.69/10.3.4.44. This vulnerability affects unknown code of the file /rps/api/json/UpdateReceivers.do of the component Replication Receiver. Executing a manipulation of the argument random can lead to os command injection. It is possible to launch the attack remotely. The exploit has been published and may be used. Upgrading to version 9.15.2.70 and 10.3.4.45 is able to resolve this issue. Upgrading the affected component is advised. The initial patch did not fix the security vulnerability properly. An update of the CVE entry to reflect this became necessary.
Description quoted from the CVE record (assigned by VulDB, published 2026-10-04).
Weakness: OS Command Injection; Command Injection
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:A
CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: total.
- On CISA KEV since
- 2026-10-14
- US federal deadline
- 2026-10-17
- Ransomware use
- Not known
Public exploit evidence (Exploit Observer)
Also known as: EUVD-2026-92078, GHSA-mxj3-2x8q-2rh9
VEDAS cluster: VEDAS:FRIGIDFEN
Exploit Observer links 2 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (2)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Nuclei template: https://raw.githubusercontent.com/projectdiscovery/nuclei-templates/main/http/cves/2026/CVE-2026-105134.yaml
- Code repository: https://github.com/rayanalmulhim/cve-2026-105134-lab
Research and write-ups (1)
- Research or write-up: https://horizon3.ai/attack-research/attack-blogs/ahsaycbs-cve-2026-105133-cve-2026-105134-technical-analysis
Vulnerability databases and vendor advisories (4)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-92078
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-mxj3-2x8q-2rh9
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-105134
- Vulnerability database or vendor advisory: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-105134
9 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.818
very likely to be attacked soon - VEDAS
- 0.981
strong exploit evidence - On CISA KEV
- Yes, since 2026-10-14
- Detection rule
- None yet
Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Ahsay AhsayCBS | version 9.15.2.0 version 9.15.2.1 version 9.15.2.2 version 9.15.2.3 version 9.15.2.4 version 9.15.2.5 version 9.15.2.6 version 9.15.2.7 and 107 more ranges | 9.15.2.70 is not affected; 10.3.4.45 is not affected |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: ahsay cloud_backup_suite.
How to fix it
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset’s internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Vendor guidance:
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
Advisories on this CVE
- Other October 2026 KEV entries (October 2026)
References
Vendor advisories and patches
Exploits and technical analysis
- VDB-413351 | Ahsay AhsayCBS Replication Receiver UpdateReceivers.do os command injection (vdb-entry, technical-description)
- CVE-2026-105134 | CVE Analysis and Report (third-party-advisory)
- Submit #942743 | Ahsay Systems Corporation Limited Ahsay CBS 10.3.0 Remote Code Execution via Arbitrary File Write (third-party-advisory)
- https://www.huntress.com/blog/ahsaycbs-flaws-exploit (broken-link, exploit)
Government sources
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-105134 (government-resource)
Other references
- VDB-413351 | CTI Indicators (IOB, IOC, TTP, IOA) (signature, permissions-required)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.