CVE-2026-105134

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreHIGH confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-04. A secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
10.0EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.8%CVSS: 10.0Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
10.0
EG Score
10.0CRITICALhigh confidence
EG Risk
50
EG Risk 50/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation2% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.8%
EPSS %ILE
78th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 4, 2026

Last Modified

October 4, 2026

Advisory Details (1)

Auto-updated Oct 4, 2026
No patch confirmed yet.
generic

AhsayCBS (DIY) v10.3.4 Release Notes (05-Aug-2026) | Ahsay Backup

https://www.ahsay.com/en/support/help-centre/release-notes/cbs/v10.3.4

Vendor Advisories for CVE-2026-105134(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 06:59 UTCGHSA enrichment
  2. 2026-10-05 03:03 UTCEG score recompute
  3. 2026-10-05 03:03 UTCGHSA enrichment
  4. 2026-10-04 23:21 UTCEPSS rescore
  5. 2026-10-04 23:06 UTCGHSA enrichment
  6. 2026-10-04 19:08 UTCGHSA enrichment
  7. 2026-10-04 15:12 UTCGHSA enrichment
  8. 2026-10-04 11:14 UTCEG score recompute
  9. 2026-10-04 11:14 UTCGHSA enrichment
  10. 2026-10-04 07:19 UTCEG score recompute
  11. 2026-10-04 07:19 UTCNVD updateCVSS v4 → 9.3
  12. 2026-10-04 06:44 UTCEG score recompute
  13. 2026-10-04 06:44 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-105134?
CVE-2026-105134 is a critical vulnerability published on October 4, 2026. 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…
When was CVE-2026-105134 disclosed?
CVE-2026-105134 was first published on October 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-105134 actively exploited?
CVE-2026-105134 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.8% probability of exploitation in the next 30 days (78th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105134?
CVE-2026-105134 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-105134?
No fix for CVE-2026-105134 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-105134 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-105134

Explore →

Is Your Infrastructure Affected by CVE-2026-105134?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs