What is CVE-2026-105133?

CVE-2026-105133 is Ahsay AhsayCBS API ApiStructsAction.java checkSysPwd improper authentication. The supplied enrichment data classifies it as Auth Bypass mapped to CWE-287 Improper Authentication.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

8 public PoC repositories reported; 2 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, identity provider logs, authentication audit logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-105133 using CVSS 7.3, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighAuth Bypasspublic exploit

CVE-2026-105133

CVE-2026-105133 — Ahsay AhsayCBS API ApiStructsAction.java checkSysPwd improper authentication

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2026-105133 in CISA KEV with 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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, 2026Updated Oct 14, 2026Sources: NVD, Ahsay (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

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

Exploitation

Confirmed

CISA KEV, listed Oct 14, 2026

EPSS

ahead of 31% of scored CVEs

Affects

Ahsay

4 products listed

CVSS base

7.3

high · 6 sources

CISA SSVC assessment

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

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade AhsayCBS to a fixed release (10.3.4). Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

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 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.

Federal deadline Oct 17, 2026 — in 2 days

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Ahsay	AhsayCBS	10.3.0	Vulnerable
Ahsay	AhsayCBS	10.3.1	Vulnerable
Ahsay	AhsayCBS	10.3.2	Vulnerable
Ahsay	AhsayCBS	10.3.4	Patched

Attack characteristics

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

Availability

Low

Confidentiality

Low

Integrity

Low

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

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

Score	Version	Severity	Expl.	Impact	Source
7.3	CVSS 3.1	high	3.9	3.4	vuldb.com (CNA), GHSA
7.5	CVSS 2.0	high	10	6.4	vuldb.com (CNA)
6.9	CVSS 4.0	medium	—	—	Ahsay (CNA)
7.3	CVSS 3.1	high	—	—	Ahsay (CNA)
7.3	CVSS 3.0	high	—	—	Ahsay (CNA)
7.5	CVSS 2.0	high	—	—	Ahsay (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-287 · Improper Authentication

Read Application Data
Gain Privileges or Assume Identity
Execute Unauthorized Code or Commands

Mitigation: Use an authentication framework or library such as the OWASP ESAPI Authentication feature.::

Weakness & attack patterns

CWE-287Improper Authentication

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-114 · Authentication AbuseCAPEC-115 · Authentication BypassCAPEC-151 · Identity SpoofingCAPEC-194 · Fake the Source of DataCAPEC-22 · Exploiting Trust in ClientCAPEC-57 · Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-593 · Session HijackingCAPEC-633 · Token ImpersonationCAPEC-650 · Upload a Web Shell to a Web ServerCAPEC-94 · Man in the Middle Attack

T1548Abuse Elevation Control Mechanism
T1040Network Sniffing
T1185Browser Session Hijacking

CISA KEV details

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

CISAThat month →

Listed

Oct 14, 2026

Federal deadline

Oct 17, 2026

in 2 days

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 date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

2 of the 5 sampled are weaponized

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

22 more posts on this CVEShowing 5 of 27 · Who is discussing this CVE, and how loudlyUnlock free

EPSS over time

FIRST rescores it daily; this is its history for as long as we have been tracking this CVE.

FIRST

Oct 4, 2026 → Oct 13, 2026 · 10 days

Detection

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

Search application, proxy, and WAF logs for requests touching /ahsay/obs/api/ApiStructsAction.java.
Prioritize edge telemetry for network-reachable AhsayCBS.
Monitor for scanner or exploit-pattern traffic after 8 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSidentity provider logsauthentication audit logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added to CISA KEV catalog
Oct 14, 2026 · CISA
Added · CVSS 3.1 7.3 (AV:N)
Oct 14, 2026 · NVD
Initial · CVE published
Oct 4, 2026 · NVD
Added · GHSA-fp2j-3cmp-828j published (medium)
Oct 4, 2026 · GitHub Security Advisory
CVE published by MITRE.
Oct 4, 2026 · SOCRadar CTI
Reported · Advisory disclosed
Oct 3, 2026 · Ahsay
Reported · VulDB entry created
Oct 3, 2026 · Ahsay
Reported · VulDB entry last update
Oct 3, 2026 · Ahsay

Source activity

Readings a source repeats on a schedule, counted rather than listed.

5×TweetsOct 9, 2026 – Oct 13, 2026 · SOCRadar CTI
4×SvrsOct 10, 2026 – Oct 12, 2026 · SOCRadar CTI
3×TelegramOct 4, 2026 – Oct 11, 2026 · SOCRadar CTI
1×CVE modified by NIST: CISA KEV details updated.Oct 14, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Oct 10, 2026 · SOCRadar CTI

References

11 on the record

vuldb.com/cve/CVE-2026-105133
Vendor Advisory
vuldb.com/submit/942688
Vendor Advisory
vuldb.com/vuln/413350
Vendor Advisory
vuldb.com/vuln/413350/cti
Vendor Advisory
www.ahsay.com/en/support/help-centre/release-notes/cbs/v10.3.4
Vendor Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-105133
US Government Resource, NIST
nvd.nist.gov/vuln/detail/CVE-2026-105133
NVD, Vendor Advisory
github.com/advisories/GHSA-fp2j-3cmp-828j
Exploit, Third Party Advisory

Coverage

9 stories from the feeds we poll

4 more reports on this CVEShowing 5 of 9 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Ahsayevery CVE for this vendor
October 2026what else CISA listed
Auth Bypasssame class
CWE-287other pages naming this weakness

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 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 record1

What should defenders know first?

CVE-2026-105133 is Ahsay AhsayCBS API ApiStructsAction.java checkSysPwd improper authentication, a high vulnerability affecting AhsayCBS from Ahsay. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 8 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.3 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.