Exploited CVEs / CVE-2026-105134

CVE-2026-105134

Ahsay AhsayCBS Command Injection Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies must remediate by 2026-10-17; treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Risk summary

CriticalCISA KEV

10.0

CVSS v3 base

9.3

CVSS v4

3.2%

EPSS exploit probability

Critical

Severity

2026-10-14

Added to KEV

2026-10-17

CISA due date

Actively exploited Ahsay AhsayCBS vulnerability, Critical severity, CVSS v3 10.0 (CVSS v4: 9.3). Added to the CISA KEV catalog 2026-10-14.

CISA required action Official fix for CVE-2026-105134 What the press says Admin questions #12 hottest CVE right now

Senserva AI Opinion and rich prompt for CVE-2026-105134

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I run IT security. Facts for CVE-2026-105134, an actively exploited vulnerability (source: https://senserva.com/cve/CVE-2026-105134.html, data from CISA KEV, FIRST.org EPSS, NVD, refreshed daily (early morning US Central)):
- CVE-2026-105134: Ahsay AhsayCBS Command Injection Vulnerability
- Affected: Ahsay AhsayCBS
- Severity: Critical, CVSS v3 10.0, CVSS v4 9.3; EPSS 30-day exploitation probability 3.2%
- Added to CISA KEV: 2026-10-14; federal remediation due 2026-10-17
- Ransomware-linked: no
- 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 dis...
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) The fastest safe path to remediation. 4) How to check whether my environment is exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch now

Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.

No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.

Do this now: Federal remediation deadline 2026-10-17; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated October 14, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2026-105134

Published: 2026-10-14
Last revised: 2026-10-14
Changes tracked: 2

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one

What changed, and when

CISA confirmed active exploitation of CVE-2026-105134 on 2026-10-14.

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

2026-10-14 CVSS 10.0 to 0.0; CVSS 0.0 to 10.0; EPSS first scored at 1.8%; added to the CISA KEV catalog by CISA
2026-10-15 EPSS 1.8% to 3.2%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal remediation due date: 2026-10-17.

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.

Official fix for CVE-2026-105134

Check the vendor's security advisory channel for the patched AhsayCBS versions and workarounds.

CISA KEV entry

Common questions about CVE-2026-105134

Is CVE-2026-105134 actively exploited?

Yes. CVE-2026-105134 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-10-14, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 3.2%.

What is the CISA deadline and required action for CVE-2026-105134?

CISA set the federal remediation due date at 2026-10-17. The verbatim 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.

What fixes CVE-2026-105134?

Check the vendor's security advisory for the patched AhsayCBS versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-105134?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-105134's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed daily (early morning US Central).

Scope and sources

More exploited Ahsay CVEs: CVE-2026-105133
Authoritative references: CVE record NVD detail CISA KEV catalog FIRST.org EPSS

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.