CVE Intelligence
CISA KEV High Authentication

CVE-2026-105133 — Ahsay AhsayCBS Improper Authentication Vulnerability

A vulnerability was detected in Ahsay AhsayCBS up to 10.3.2. This affects the function checkSysPwd of the file com/ahsay/obs/api/ApiStructsAction.java of the component API. Performing a manipulation of the argument random results in improper authentication. It is possible to initiate the attack remotely. The exploit is now public and may be used. Upgrading to version 10.3.4 is able to mitigate this issue. It is recommended to upgrade the affected component.

Published Oct 4, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, CISA Known Exploited Vulnerabilities, GitHub Security Advisories · CNA: VulDB

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · Oct 14, 2026
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • EPSS 0.4% (30-day exploitation probability)+5
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

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

Exploitation
Confirmed
CISA KEV, listed Oct 14, 2026
EPSS FIRST
0.38%
ahead of 31% of scored CVEs · Oct 14, 2026
Affects
Ahsay
AhsayCBS and 1 more
CVSS base
7.3
High · 3 source(s)

CISA SSVC assessment CISA

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

Exploitation
Active
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

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.

US federal deadline: Oct 17, 2026 — due in 2 day(s)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Ahsay AhsayCBS, Ahsay Cloud Backup Suite).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  5. Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Ahsay AhsayCBS version 10.3.0version 10.3.1version 10.3.2 Vulnerable CVE Program (cve.org) e CISA ADP
Ahsay Cloud Backup Suite < 10.3.4 Vulnerable NIST National Vulnerability Database

Attack characteristics

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Every base score collected

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

ScoreVersionSeverityExpl.ImpactScored by
6.9 CVSS 4.0 Medium — — VulDB via CVE Program (cve.org) e CISA ADP
5.5 CVSS 4.0 Medium — — cna@vuldb.com via NIST National Vulnerability Database
7.3 CVSS 3.1 High 3.9 3.4 cna@vuldb.com via NIST National Vulnerability Database
7.3 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.3 CVSS 3.1 High — — VulDB via CVE Program (cve.org) e CISA ADP
7.3 CVSS 3.0 High — — VulDB via CVE Program (cve.org) e CISA ADP
7.5 CVSS 2.0 High 10.0 6.4 cna@vuldb.com via NIST National Vulnerability Database
7.5 CVSS 2.0 High — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L (score shown at the top: cna@vuldb.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-287 · Improper Authentication

Other CVEs with this weakness →

CISA KEV details CISA

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

Listed
Oct 14, 2026
Federal deadline
Oct 17, 2026
due in 2 day(s)
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 reference date.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.38%

Detection

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

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.
  • Hunt retroactively in logs from before Oct 14, 2026 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · ahsay/cloud backup suite
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · Undergoing Analysis → Analyzed
    Oct 15, 2026 · NIST National Vulnerability Database
  • SSVC assessment updated
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Deferred → Undergoing Analysis
    Oct 14, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 14, 2026 · CISA Known Exploited Vulnerabilities
  • Added to CISA KEV catalog
    Oct 13, 2026 · CISA
  • Affected products added · ahsay/ahsaycbs
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 7.3
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Deferred
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 4, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

8 on the record

Elsewhere on this site

Ahsay
every CVE for this vendor
2026-10
what else CISA listed that month
Authentication
same class
CWE-287
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-105134 Ahsay AhsayCBS Command Injection Vulnerability KEV 11d

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 fixed version, patch or mitigation documented.
  • 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 record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-105133 is "Ahsay AhsayCBS Improper Authentication Vulnerability", rated High. It affects AhsayCBS (Ahsay); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.3 describes technical severity. EPSS 0.38% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.