Skip to content
vulnerability

CVE-2026-105134

10.0
Critical
KEV · Exploited in wildEPSS 82%Patch available

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.

exploited
Yes, in CISA KEV since 14 Oct 2026fix by 17 Oct 2026 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
Fixed in 9.15.2.70, 10.3.4.45
likelihood
EPSS 81.8%
Published 4 Oct 2026Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstUpgrade to a fixed release: 9.15.2.70, 10.3.4.45.

triage
server-sideruntimeWAF can block: partlyAV · networkCWE-77· Command InjectionCWE-78· OS Command Injection

Can a WAF block it? Partly. The attack is delivered via an HTTP request to a specific API endpoint with a manipulated parameter 'random' that leads to command injection. This unusual parameter manipulation can be detected and blocked by a WAF rule targeting this endpoint and parameter. A WAF rule can match manipulation of the argument random in /rps/api/json/UpdateReceivers.do. No tracked WAF vendor has published a rule for this CVE yet, so you would write it yourself.

What a custom rule would match: manipulation of the argument random in /rps/api/json/UpdateReceivers.do

Also consider: patch · custom WAF rule · input validation · RASP · shlex/execve-style APIs

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionnonescopechangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
common questions

Is CVE-2026-105134 being exploited?

Yes. CVE-2026-105134 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-105134?

CVE-2026-105134 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-105134?

Yes. A fix has been recorded for CVE-2026-105134. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-105134 affect?

CVE-2026-105134 affects ahsay:cloud_backup_suite. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
ahsay:cloud_backup_suite
affected versions
Ahsay AhsayCBS
  • affected9.15.2.0
  • affected9.15.2.1
  • affected9.15.2.2
  • affected9.15.2.3
  • affected9.15.2.4
  • affected9.15.2.5
  • affected9.15.2.6
  • affected9.15.2.7
  • affected9.15.2.8
  • affected9.15.2.9
  • affected9.15.2.10
  • affected9.15.2.11
  • affected9.15.2.12
  • affected9.15.2.13
  • affected9.15.2.14
  • affected9.15.2.15
  • affected9.15.2.16
  • affected9.15.2.17
  • affected9.15.2.18
  • affected9.15.2.19
  • affected9.15.2.20
  • affected9.15.2.21
  • affected9.15.2.22
  • affected9.15.2.23
  • affected9.15.2.24
  • affected9.15.2.25
  • affected9.15.2.26
  • affected9.15.2.27
  • affected9.15.2.28
  • affected9.15.2.29
  • affected9.15.2.30
  • affected9.15.2.31
  • affected9.15.2.32
  • affected9.15.2.33
  • affected9.15.2.34
  • affected9.15.2.35
  • affected9.15.2.36
  • affected9.15.2.37
  • affected9.15.2.38
  • affected9.15.2.39
  • affected9.15.2.40
  • affected9.15.2.41
  • affected9.15.2.42
  • affected9.15.2.43
  • affected9.15.2.44
  • affected9.15.2.45
  • affected9.15.2.46
  • affected9.15.2.47
  • affected9.15.2.48
  • affected9.15.2.49
  • affected9.15.2.50
  • affected9.15.2.51
  • affected9.15.2.52
  • affected9.15.2.53
  • affected9.15.2.54
  • affected9.15.2.55
  • affected9.15.2.56
  • affected9.15.2.57
  • affected9.15.2.58
  • affected9.15.2.59
  • affected9.15.2.60
  • affected9.15.2.61
  • affected9.15.2.62
  • affected9.15.2.63
  • affected9.15.2.64
  • affected9.15.2.65
  • affected9.15.2.66
  • affected9.15.2.67
  • affected9.15.2.68
  • affected9.15.2.69
  • affected10.3.4.0
  • affected10.3.4.1
  • affected10.3.4.2
  • affected10.3.4.3
  • affected10.3.4.4
  • affected10.3.4.5
  • affected10.3.4.6
  • affected10.3.4.7
  • affected10.3.4.8
  • affected10.3.4.9
  • affected10.3.4.10
  • affected10.3.4.11
  • affected10.3.4.12
  • affected10.3.4.13
  • affected10.3.4.14
  • affected10.3.4.15
  • affected10.3.4.16
  • affected10.3.4.17
  • affected10.3.4.18
  • affected10.3.4.19
  • affected10.3.4.20
  • affected10.3.4.21
  • affected10.3.4.22
  • affected10.3.4.23
  • affected10.3.4.24
  • affected10.3.4.25
  • affected10.3.4.26
  • affected10.3.4.27
  • affected10.3.4.28
  • affected10.3.4.29
  • affected10.3.4.30
  • affected10.3.4.31
  • affected10.3.4.32
  • affected10.3.4.33
  • affected10.3.4.34
  • affected10.3.4.35
  • affected10.3.4.36
  • affected10.3.4.37
  • affected10.3.4.38
  • affected10.3.4.39
  • affected10.3.4.40
  • affected10.3.4.41
  • affected10.3.4.42
  • affected10.3.4.43
  • affected10.3.4.44
vendor says fixed in9.15.2.70, 10.3.4.45

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept · 1 Nuclei template

Nuclei
GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
yes
technical impact
total

Assessed by CISA 14 Oct 2026 (SSVC 2.0.3).

timeline

  1. 4 Oct 2026Published
  2. 5 Oct 2026First proof-of-concept repository on GitHub (unvetted) · 1 day later
  3. 14 Oct 2026Added to CISA KEV (exploited in the wild) · 9 days later
  4. 14 Oct 2026CISA SSVC assessment: exploitation active · same day later
  5. 17 Oct 2026CISA remediation due date (US federal agencies) · 3 days later
  6. 26 Oct 2026CVE record last updated · 10 days later
  7. 2 Nov 2026Analysed by vulneraibility.com · 7 days later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
7 references in the CVE record: 2 advisories, 1 patch, 1 exploit, 3 links

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved