AhsayCBS auth bypass, exploited in wild (CVE-2026-105133) [PoC]
CVE-2026-105133
CVE-2026-105133: AhsayCBS up to 10.3.2 authentication bypass is actively exploited in the wild (CVSS 7.5). Upgrade to 10.3.4 now to close the API hole.
Actively exploited in the wild - CVE-2026-105133 is a high severity authentication bypass in Ahsay AhsayCBS up to 10.3.2 that lets a remote attacker with no credentials defeat the API login check by manipulating the random parameter. Public exploit code is circulating and the flaw is confirmed as exploited in the wild, so treat any internet exposed AhsayCBS console as untrusted until you upgrade to 10.3.4.
Overview
AhsayCBS is the centralized backup server component of the Ahsay backup platform, commonly deployed by managed service providers to hold client backup data, credentials, and scheduling logic. It exposes an API that handles authentication through the class com.ahsay.obs.api.ApiStructsAction, specifically the checkSysPwd function.
CVE-2026-105133 is an improper authentication weakness in that function. When an attacker manipulates the random argument during the authentication exchange, the server can be tricked into accepting a login it should have rejected. No username, password, or prior session is required, and no user interaction is needed on the victim side. The attack travels over the network, and both the technical details and working exploit code are public.
The vendor addressed the issue in AhsayCBS 10.3.4.
Impact
A successful bypass gives an attacker an authenticated foothold in the backup management console. From there the blast radius is severe because backup servers are high value targets: they aggregate credentials, retention policies, and restore points for every protected endpoint. An intruder who reaches the console can generally enumerate backup sets, read or alter job configuration, and in many deployments trigger restores that overwrite production data. Ransomware operators have repeatedly targeted backup infrastructure specifically to eliminate recovery options before encrypting production systems, which makes a pre-authentication bypass on this class of appliance especially dangerous.
Because the CVSS vector is network reachable, low complexity, no privileges, and no user interaction, the only meaningful precondition is that the AhsayCBS console or API is exposed to an untrusted network.
Remediation and Mitigation
- Upgrade AhsayCBS to version 10.3.4 or later. This is the vendor supported fix and the only complete remediation.
- If you cannot upgrade immediately, remove the AhsayCBS management console and API from direct internet exposure. Place it behind a VPN, an allowlisted reverse proxy, or a zero trust access gateway.
- Restrict inbound access to the console ports with firewall rules limited to known administrative source addresses.
- Review authentication and API logs for unexpected or failed
checkSysPwdcalls, anomalous source IP addresses, and logins outside normal administrative hours. - Rotate administrative credentials and any API tokens stored in the appliance, and verify that no unauthorized backup jobs, restore tasks, or new administrative accounts were created.
- Where the appliance was internet facing and unpatched, treat the host as potentially compromised and perform a full forensic review before trusting it for recovery.
For incident reporting and related coverage, see breach reports and security news.
Security Insight
The EPSS score for CVE-2026-105133 is only around 0.4 percent, yet CISA has confirmed active exploitation. That gap is the story: EPSS models broad opportunistic scanning, while backup infrastructure is attacked deliberately by small numbers of motivated actors. It also mirrors earlier episodes where authentication checks buried inside API structs were reached and manipulated, a pattern that suggests authentication logic in this product has historically been spread across too many handlers rather than centralized. For defenders, the takeaway is that a low EPSS number is not a reason to deprioritize a pre-authentication bypass in backup software.
Further Reading
Never miss a critical vulnerability
Get real-time security alerts delivered to your preferred platform.
Public PoC References
Unverified third-party code
These repositories are publicly listed on GitHub and have not been audited by Yazoul Security. They may contain malware, backdoors, destructive payloads, or operational security risks (telemetry, exfiltration). Treat them as hostile binaries. Inspect source before execution. Run only in isolated, disposable lab environments (offline VM, no credentials, no production data).
Authorized use only. This information is provided for defensive research, detection engineering, and patch validation. Using exploit code against systems you do not own or do not have explicit written permission to test is illegal in most jurisdictions and violates Yazoul's terms of use.
| Repository | Stars |
|---|---|
| horizon3ai/AhsayCBS-Auth-Bypass-RCE A proof of concept exploit for CVE-2026-105133 and CVE-2026-105134 affecting AhsayCBS | ★ 1 |
Showing 1 of 1 known references. Source: nomi-sec/PoC-in-GitHub.
Related Advisories
JFrog Artifactory could return an internal anonymous-user token to an unauthenticated caller when anonymous access is disabled, potentially exposing sensitive resources....
LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.84.0, LiteLLM's MCP Streamable HTTP endpoint allowed an unauthenticated attacker to use a fabricated Au...
A vulnerability was identified in kodcloud KodExplorer up to 4.52. This impacts the function fileGet of the file /app/controller/share.class.php of the component fileGet Endpoint. Such manipulation of...
A vulnerability was identified in liangliangyy DjangoBlog up to 2.1.0.0. The impacted element is an unknown function of the file owntracks/views.py of the component logtracks Endpoint. The manipulatio...