What is CVE-2026-105134?

CVE-2026-105134 is Ahsay AhsayCBS Replication Receiver UpdateReceivers.do os command injection. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-78 OS Command Injection; CWE-77 Command Injection.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

8 public PoC repositories reported; 2 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-105134 using CVSS 10, EPSS 2%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVcriticalRemote Code Execpublic exploit

CVE-2026-105134

CVE-2026-105134 — Ahsay AhsayCBS Replication Receiver UpdateReceivers.do os command injection

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2026-105134 in CISA KEV with 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

A flaw has been found in Ahsay AhsayCBS up to 10.3.2. 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 10.3.4 is able to resolve this issue. Upgrading the affected component is advised.

Published Oct 4, 2026Updated Oct 14, 2026Sources: NVD, Ahsay (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Oct 14, 2026

EPSS

ahead of 79% of scored CVEs

Affects

Ahsay

4 products listed

CVSS base

critical · 6 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade AhsayCBS to a fixed release (10.3.4). Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

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.

Federal deadline Oct 17, 2026 — in 2 days

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Ahsay	AhsayCBS	10.3.0	Vulnerable
Ahsay	AhsayCBS	10.3.1	Vulnerable
Ahsay	AhsayCBS	10.3.2	Vulnerable
Ahsay	AhsayCBS	10.3.4	Patched

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Changed

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
10	CVSS 3.1	critical	3.9	6	vuldb.com (CNA), GHSA
10	CVSS 2.0	high	10	10	vuldb.com (CNA)
10	CVSS 4.0	critical	—	—	Ahsay (CNA)
10	CVSS 3.1	critical	—	—	Ahsay (CNA)
10	CVSS 3.0	critical	—	—	Ahsay (CNA)
10	CVSS 2.0	critical	—	—	Ahsay (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Execute Unauthorized Code or Commands
DoS: Crash, Exit, or Restart
Read Files or Directories
Modify Files or Directories

Mitigation: If at all possible, use library calls rather than external processes to recreate the desired functionality.

CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')

Execute Unauthorized Code or Commands

Mitigation: If at all possible, use library calls rather than external processes to recreate the desired functionality.

Weakness & attack patterns

CWE-78OS Command Injection
CWE-77Command Injection

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-248 · Command InjectionCAPEC-40 · Manipulating Writeable Terminal DevicesCAPEC-15 · Command DelimitersCAPEC-136 · LDAP InjectionCAPEC-76 · Manipulating Web Input to File System CallsCAPEC-43 · Exploiting Multiple Input Interpretation LayersCAPEC-183 · IMAP/SMTP Command InjectionCAPEC-75 · Manipulating Writeable Configuration Files

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Oct 14, 2026

Federal deadline

Oct 17, 2026

in 2 days

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

2 of the 5 sampled are weaponized

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

24 more posts on this CVEShowing 5 of 29 · Who is discussing this CVE, and how loudlyUnlock free

EPSS over time

FIRST rescores it daily; this is its history for as long as we have been tracking this CVE.

FIRST

Oct 4, 2026 → Oct 13, 2026 · 10 days

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /rps/api/json/UpdateReceivers.do.
Prioritize edge telemetry for network-reachable AhsayCBS.
Monitor for scanner or exploit-pattern traffic after 8 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added to CISA KEV catalog
Oct 14, 2026 · CISA
Added · CVSS 3.1 10.0 (AV:N)
Oct 14, 2026 · NVD
Initial · CVE published
Oct 4, 2026 · NVD
Added · GHSA-mxj3-2x8q-2rh9 published (critical)
Oct 4, 2026 · GitHub Security Advisory
CVE published by MITRE.
Oct 4, 2026 · SOCRadar CTI
Reported · Advisory disclosed
Oct 3, 2026 · Ahsay
Reported · VulDB entry created
Oct 3, 2026 · Ahsay
Reported · VulDB entry last update
Oct 3, 2026 · Ahsay

Source activity

Readings a source repeats on a schedule, counted rather than listed.

10×TweetsOct 4, 2026 – Oct 13, 2026 · SOCRadar CTI
8×ModifiedOct 4, 2026 – Oct 14, 2026 · SOCRadar CTI
6×SvrsOct 5, 2026 – Oct 12, 2026 · SOCRadar CTI
3×TelegramOct 4, 2026 – Oct 11, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Oct 5, 2026 · SOCRadar CTI
1×Github_Repos · Github repository created, RayanAlmulhim/CVE-2026-105134-labOct 5, 2026 · SOCRadar CTI

References

11 on the record

vuldb.com/cve/CVE-2026-105134
Vendor Advisory
vuldb.com/submit/942743
Vendor Advisory
vuldb.com/vuln/413351
Vendor Advisory
vuldb.com/vuln/413351/cti
Vendor Advisory
www.ahsay.com/en/support/help-centre/release-notes/cbs/v10.3.4
Vendor Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-105134
US Government Resource, NIST
nvd.nist.gov/vuln/detail/CVE-2026-105134
NVD, Vendor Advisory
github.com/advisories/GHSA-mxj3-2x8q-2rh9
Exploit, Third Party Advisory

Coverage

8 stories from the feeds we poll

3 more reports on this CVEShowing 5 of 8 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Ahsayevery CVE for this vendor
October 2026what else CISA listed
Remote Code Execsame class
CWE-78other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-105134 is Ahsay AhsayCBS Replication Receiver UpdateReceivers.do os command injection, a critical vulnerability affecting AhsayCBS from Ahsay. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 8 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 10 describes technical severity, while EPSS 2% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.