Advisory

CVE-2026-105134: Ahsay AhsayCBS Command Injection Vulnerability — what to do now

CVE-2026-105134 affects Ahsay AhsayCBS and is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog — it is being exploited in the wild, rated CRITICAL (CVSS 10). Here is what it is, who is affected, and the response. No exploit details.

TL;DR: CVE-2026-105134 is a known-exploited vulnerability in Ahsay AhsayCBS. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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. Then confirm no exposed, unpatched instance remains on your perimeter.

What CVE-2026-105134 is

According to the public vulnerability record, 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.

CISA summarises it as: Ahsay AhsayCBS contains a command injection vulnerability that could allow a remote attacker to execute operating system commands via manipulation of the random parameter in the Replication Receiver component’s /rps/api/json/UpdateReceivers.do endpoint. This vulnerability can be chained with CVE-2026-105133.

Affected product & severity

CVE-2026-105134 affects Ahsay AhsayCBS. Confirm exact affected and fixed versions against the vendor's advisory.

PropertyDetail
CVECVE-2026-105134
VendorAhsay
ProductAhsayCBS
CVSS10 (CRITICAL)
VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
WeaknessCWE-77, CWE-78
Added to CISA KEV2026-10-14

Why it is urgent

This CVE is in the CISA Known Exploited Vulnerabilities (KEV) catalog (added 2026-10-14) — a list of flaws with confirmed exploitation in the wild. US federal agencies are required to remediate KEV entries on a deadline; for everyone else it is a strong signal to prioritise this now rather than wait. There is no proof-of-concept or exploit detail in this advisory by design.

What to do now

  1. Follow CISA's required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.
  2. Apply the vendor's patch or mitigation for Ahsay AhsayCBS on every affected instance, per the official advisory linked below.
  3. Inventory every instance — production, staging, legacy and third-party appliances that bundle it. You cannot patch what you have forgotten you run.
  4. Verify the version actually deployed, not the one you think you run; the risk is the build actually serving traffic.
  5. Check for internet exposure. A known-exploited flaw on a reachable instance is an active risk — confirm none is exposed that should not be.

How to confirm your exposure

The hard part of a known-exploited CVE is rarely the patch — it is knowing where a reachable, unpatched instance still exists: a forgotten host, a staging box that drifted public, a third-party appliance. AssurePort's network and host penetration testing discovers exposed services, fingerprints their versions, and correlates them against known-exploited vulnerabilities — so a newly-weaponised CVE is checked against your real external footprint, including the hosts you don't have on a list. That is the window continuous testing is built to close.

Sources & further reading: NVD CVE-2026-105134 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: vuldb.com, vuldb.com, vuldb.com, vuldb.com. This advisory contains no exploit code.

Frequently asked questions

What is CVE-2026-105134?

CVE-2026-105134 is a vulnerability in Ahsay AhsayCBS, rated CRITICAL (CVSS 10), listed in the CISA Known Exploited Vulnerabilities catalog. 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.

Is CVE-2026-105134 being exploited?

Yes — it is in the CISA KEV catalog (added 2026-10-14), which lists vulnerabilities with confirmed in-the-wild exploitation. Treat it as an active, prioritise-now risk.

Which products are affected?

Ahsay AhsayCBS. Confirm the exact affected and fixed versions against the vendor's official security advisory before acting.

What should I do right now?

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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. Then inventory every instance, verify the version actually deployed, and confirm none is exposed and unpatched on your perimeter.