Skip to main content
Type Vulnerability

Ahsay · Code execution

Ahsay AhsayCBS Command Injection Vulnerability

3 sourcesCVE-2026-105133CVE-2026-105134CVE-2026-0322+1 more

At a glance

High
Suggested 24-hour window, counted from the last update
ActiveConfirmed in-the-wild exploitation
Evidence-weighted, not popularity
Signal

Actively exploited in the wild — prioritise confirming exposure.

Why High

High rather than Critical: exposure is scored at a default because we cannot see your systems or suppliers. If you run or depend on AhsayCBS, treat it as Critical.

Briefing

  • IT leaders should assess whether Ahsay AhsayCBS is present in their estate and review associated security controls.
  • Business leaders should consider the potential impact of a confirmed exploited vulnerability in critical systems.
  • Leaders should monitor for potential exploitation attempts related to CVE-2026-105134 with a 1.8% estimated attack probability.

Questions to ask IT

  • Do we run AhsayCBS, and which versions?
  • Is any of it reachable from the internet?
  • Have we checked whether it has already been used against us?
  • If it is still not patched, what mitigation is in place, and what is holding the fix up?

Next steps

  1. Confirm exposure and remediation status for affected products

Summary

  • 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.
  • CVE-2026-105134 is confirmed as exploited in the wild (US known-exploited catalogue).
  • CVE-2026-105134 has an estimated ~1.8% chance of attack in 30 days (78.6th percentile) as of 2026-10-14 — probability signal, not confirmed exploitation.

Read the original reportSecurityWeek(opens in a new tab)

Products and services involved

  • AhsayCBS88% match confidence · CVE-2026-105133

All 15 reports in this story

Same event, different frames

Distinct often headline the same incident differently.

Pulse

Last checked 3d ago · Recheck overdue since 6 Nov 2026, 10:34 UK time

Signal
5 Nov 2026, 10:34 UK time · 3d ago

in the next 30 days rose from 1.8% to 81.8% — now an elevated likelihood signal.

rose materially — review inventory match and patch cadence.

EscalationDe-escalationCritical / liveWhat these mean
Drag to pan · Ctrl / ⌘ + scroll or pinch to zoom8 events

Sources

How we know

Statements extracted from sources. Higher confidence means stronger corroboration.

  • ConfirmedHeadline90% confidence

    Ahsay AhsayCBS Command Injection Vulnerability

  • ConfirmedSummary fact75% confidence

    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.

  • ConfirmedCVE identifier95% confidence

    Event involves CVE-2026-105134

  • ConfirmedKnown-exploited catalogue98% confidence

    CVE-2026-105134 is confirmed as exploited in the wild (US known-exploited catalogue)

  • ConfirmedEstimated attack likelihood95% confidence

    CVE-2026-105134 has an estimated ~1.8% chance of attack in 30 days (78.6th percentile) as of 2026-10-14 — probability signal, not confirmed exploitation

  • ConfirmedCVE identifier95% confidence

    Event involves CVE-2026-105133

  • ConfirmedKnown-exploited catalogue98% confidence

    CVE-2026-105133 is confirmed as exploited in the wild (US known-exploited catalogue)