AhsayCBS CVE-2026-105134: a backup console that executes what a stranger sends

A backup server is the last line of an organisation's recovery plan. CVE-2026-105134 makes one model of that server execute attacker-supplied shell commands through an HTTP endpoint, and NVD scores it 10.0.
The record describes command injection in /rps/api/json/UpdateReceivers.do on AhsayCBS up to 10.3.2, fixed in 10.3.4. The same advisory set includes CVE-2026-105133, an authentication weakness in the API component that NVD scores 7.3, with the exploit described as public. Both were added to the KEV catalog on 2026-10-14.

Why the replication endpoint matters

Replication receivers exist so that one backup node can accept data from another. To do that, they authenticate peers and process structured requests. A flaw in that path is reachable by anyone who can talk to the API, and the resulting command runs with the privileges of the backup service.
Backup services sit close to the things that matter. They read files from servers that grant them write access, they hold repository credentials, and they often have a route into storage systems that are otherwise isolated. A command executed in that context is not contained.

The authentication companion

CVE-2026-105133 involves manipulation of a parameter in a password-check function. Read alongside the command injection, the pair suggests an API surface where trust decisions were made per-endpoint rather than centrally. The pattern is worth looking for during the upgrade, because it hints at what else may need review.

Practical exposure check

AhsayCBS instances are frequently internet-facing so that remote agents can check in. ZoomEye fingerprint queries are a reasonable way to see how many consoles advertise the product, but the fingerprint is not proof of a specific version. Treat any count as an inventory prompt rather than a vulnerability claim.
For your own estate, answer these questions: which AhsayCBS consoles answer from the internet, which of them are below 10.3.4, and which of them hold credentials for other systems.

Recovery is the real test

Backup infrastructure is the one place where incident response and business continuity are the same conversation. Before patching, capture the console's configuration and its list of protected sources. After patching, rotate repository credentials and any account the backup service uses to read from production, because a command executed as the backup service could have read them.
Then verify the restore path. An organisation that discovers during an incident that its backup console was compromised needs a copy of the data that the attacker never touched. Offline or immutable copies are the only reliable version of that promise.