# CVE-2026-105134: Ahsay AhsayCBS Command Injection

> Remote attackers can execute arbitrary OS commands via the random argument in the Replication Receiver API, requiring an upgrade to mitigate.

- **Severity:** Critical 10.0 (`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`)
- **Exploited in the wild:** Yes, since 14 Oct 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-mxj3-2x8q-2rh9

## What is CVE-2026-105134?

CVE-2026-105134 is a critical command injection vulnerability in AhsayCBS, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-105134?

It affects 1 product.


Products: Ahsay Cloud Backup Suite.

## How do I fix CVE-2026-105134?

No fix has been published for CVE-2026-105134 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 17 Oct 2026.

## Is CVE-2026-105134 being exploited?

Yes. Attackers have exploited CVE-2026-105134 in the wild since at least 14 Oct 2026.

Public exploit code:

- Educational lab and clean-room reproduction demonstrating the OS command injection pattern in CVE-2026-105134. For defensive research only. (github_poc): https://github.com/RayanAlmulhim/CVE-2026-105134-lab
- AhsayCBS <= 10.3.4 - Unauthenticated RCE (nuclei): http/cves/2026/CVE-2026-105134.yaml

## Other vulnerabilities in AhsayCBS

- [CVE-2026-105133](https://insights.sbomify.com/CVE-2026-105133/): Ahsay AhsayCBS Improper Authentication (medium 6.9, exploited in the wild)
- [CVE-2020-5846](https://insights.sbomify.com/CVE-2020-5846/): File upload in n/a (high 8.8)
- [CVE-2019-10267](https://insights.sbomify.com/CVE-2019-10267/): File upload in n/a (high 8.8)
- [CVE-2019-10265](https://insights.sbomify.com/CVE-2019-10265/): Path traversal in n/a (high 7.5)
- [CVE-2019-10266](https://insights.sbomify.com/CVE-2019-10266/): XML external entity in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-105134 and fix it if it is affected.

What it is: CVE-2026-105134 is a critical command injection vulnerability in AhsayCBS, published on 4 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-105134 in the wild since at least 14 Oct 2026.

Affected product: AhsayCBS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-105134/ (Markdown: https://insights.sbomify.com/CVE-2026-105134/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-105134
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-105134
- OSV: https://osv.dev/vulnerability/CVE-2026-105134

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-105134/
Summaries are generated and may contain mistakes; the official description above is the record.