← Back to Feed CACHED · 2026-10-15 07:53:56 · CACHE_KEY CVE-2026-105133
CVE-2026-105133 · CWE-287 · Disclosed 2026-10-04

AhsayCBS Improper Authentication Bypass via FromServlet Parameter

ASSESSED — NOISGATE
Vendor
—
—
—
Reassessed
—
—
—
Verdict: —
Do you agree?
01 · The Real Story

Someone left the master key to the vault taped to the front door, and burglars already found it

CVE-2026-105133 is an authentication bypass in Ahsay Cloud Backup Server (AhsayCBS) affecting all versions through 10.3.2 — and initially through 10.3.4.0 as well, since the first patch attempt failed. The flaw lives in the checkSysPwd() function of com/ahsay/obs/api/ApiStructsAction.java: any request carrying "FromServlet":"Y" in the JSON body skips the system-password check entirely. No credentials, no tokens, no user interaction. The result is full unauthenticated access to the AhsayCBS management API. In the wild, attackers chain this with CVE-2026-105134 (a path-traversal file-upload bug scoring CVSS 10.0) to drop JSP webshells and run code as SYSTEM. Affected versions span AhsayCBS v7, v8, v9, and v10 lines. Verified fixes are hotfix v10.3.4.45 and v9.15.2.70; v7/v8 users must first upgrade to v9.15.0.0 before applying v9.15.2.70.

The vendor’s CVSS 7.3 HIGH rating with C:L/I:L/A:L impact is technically accurate in isolation — the auth bypass alone does not directly exfiltrate data or execute code. But this score is dangerously misleading. In every real-world exploitation observed since October 7, 2026, CVE-2026-105133 is chained with CVE-2026-105134 for full unauthenticated RCE as SYSTEM on a backup control plane — a server that by definition holds credentials, encryption keys, and recovery data for every protected host in the environment. Five organizations were compromised within 24 hours. CISA added this to the KEV catalog on October 14 with a remediation deadline of October 17 — a 3-day window that signals how seriously the federal government treats this. The vendor’s 7.3 does not capture the blast radius of a compromised backup server in an MSP environment, where one AhsayCBS instance may manage hundreds of customer environments.

"Backup server auth bypass is actively exploited; your recovery plane is the target."
02 · The Attack Path

5 steps from start to impact.

STEP 01

Identify internet-exposed AhsayCBS management console

The attacker scans for AhsayCBS web interfaces, typically on port 443 or 8443. The Tomcat-based management console exposes identifiable paths like /obs/api/ and Ahsay branding. Many MSPs expose this interface publicly so customer backup agents can connect. Shodan/FOFA/Censys dorks for the Ahsay login page or API paths will enumerate targets.
Conditions required:
  • AhsayCBS management interface reachable over the network
Where this breaks in practice:
  • Some deployments restrict the management port to VPN or internal networks only
  • Smaller installations may be behind NAT without port forwarding
Detection/coverage: Shodan dork: http.title:"AhsayCBS" or http.html:"ahsay" on ports 443/8443. Censys search for AhsayCBS certificate subjects.
STEP 02

Bypass authentication via FromServlet parameter

The attacker sends a crafted JSON request to the AhsayCBS API with "FromServlet":"Y" in the body. This causes the checkSysPwd() function to skip password validation entirely, granting unauthenticated access to all administrative API endpoints. The Horizon3.ai public PoC (horizon3ai/AhsayCBS-Auth-Bypass-RCE) automates this step. No credentials, cookies, or tokens are required.
Conditions required:
  • Network access to the AhsayCBS API endpoint
  • No WAF or API gateway blocking the FromServlet parameter
Where this breaks in practice:
  • A well-configured WAF inspecting JSON payloads could block the specific parameter, but this is a very specific rule that almost no one has
Detection/coverage: WAF rules inspecting for FromServlet in JSON request bodies. IDS signature for anomalous API access patterns to /obs/api/ without prior authentication.
STEP 03

Upload JSP webshell via path traversal (CVE-2026-105134)

With authentication bypassed, the attacker hits the replication receiver file upload endpoint (PUT /rps/obs7/rpsfile/upload) and exploits a path traversal to write a JSP webshell into the Tomcat webapps directory. The file is immediately accessible via HTTP and executes under the AhsayCBS service account — typically SYSTEM on Windows or root on Linux. This is CVE-2026-105134 (CVSS 10.0) and is inseparable from the exploitation chain observed in the wild.
Conditions required:
  • Successful auth bypass from step 2
  • AhsayCBS replication receiver endpoint accessible
  • Writable Tomcat webapps directory (default configuration)
Where this breaks in practice:
  • Application-layer file integrity monitoring on the webapps directory could detect new JSP files
  • Endpoint detection of JSP webshell content patterns
Detection/coverage: EDR alerts on new .jsp file creation under %CBS_HOME%\webapps or the equivalent Linux path. YARA rules for common JSP webshell patterns.
STEP 04

Execute commands as SYSTEM and establish persistence

Through the webshell, the attacker executes OS commands with the privileges of the AhsayCBS service account. Observed payloads include XMRig cryptominers disguised as msedge.exe, a modified NSSM utility creating a persistence service named MicrosoftEdgeUpdateSvc, and a kernel driver (WinRing0x64.sys) for ring-0 miner access. The PowerShell dropper Taskgmr.ps1 downloads payloads from imagefiles-backup.oss-ap-southeast-7.aliyuncs[.]com.
Conditions required:
  • Successful webshell deployment from step 3
  • Outbound internet access for payload retrieval
Where this breaks in practice:
  • EDR should detect webshell-spawned process chains, cryptominer binaries, and NSSM-based persistence
  • Network monitoring should flag connections to known mining pools like xmr.kryptex[.]network:8029
Detection/coverage: EDR detection of cmd.exe/powershell.exe spawned by java.exe (Tomcat). Network IOC matching for xmr.kryptex[.]network and Aliyun staging infrastructure.
STEP 05

Compromise backup data and pivot to managed environments

With SYSTEM access on the backup server, the attacker can access all stored backup data, encryption keys, backup credentials for protected hosts, and potentially replication targets. In an MSP deployment, this means access to backup data for every customer environment managed by this AhsayCBS instance. The attacker can exfiltrate data, destroy backups to enable ransomware (no recovery), or use stored credentials to pivot into customer networks.
Conditions required:
  • SYSTEM access on AhsayCBS host
  • AhsayCBS managing multiple customer environments (typical for MSPs)
Where this breaks in practice:
  • Backup encryption with externally managed keys limits data access
  • Network segmentation between backup infrastructure and production environments
Detection/coverage: Anomalous bulk data access or exfiltration from backup storage. Unexpected credential usage from the backup server to managed hosts.
03 · Compensating Control

1
CRITICAL 9.2→HIGH 7.0
SEVERITY REDUCED
Block public access to AhsayCBS management interface immediately — Apply IP allowlisting or place the AhsayCBS management console (ports 443/8443) behind a VPN gateway. This breaks step 1 of the attack path by making the API endpoint unreachable from the internet. Per the noisgate mitigation SLA for CRITICAL, deploy within 3 days — but given active exploitation and KEV listing, implement within hours. Customer backup agents can be routed through the VPN or a dedicated reverse proxy with mutual TLS.
2
CRITICAL 9.2→LOW 2.0
SEVERITY REDUCED
Apply verified hotfix v10.3.4.45 or v9.15.2.70 — These are the only verified fixes as of October 12, 2026. Do NOT rely on v10.3.4.0 — it does not close the vulnerability. For v7/v8 installations, upgrade to v9.15.0.0 first, then apply v9.15.2.70. Requires a service restart. Per the noisgate remediation SLA for CRITICAL, complete within 90 days, but given KEV and active exploitation, patch immediately after testing. Schedule an emergency maintenance window.
3
CRITICAL 9.2→HIGH 6.5
SEVERITY REDUCED
Deploy WAF rule blocking FromServlet parameter in JSON bodies — Add a WAF or reverse proxy rule that inspects JSON request bodies to the AhsayCBS API and blocks any request containing the key FromServlet. This directly neutralizes the auth bypass mechanism. This is a targeted compensating control if patching or network isolation cannot be completed immediately. Note: this is fragile and may be bypassable with encoding tricks — treat as a temporary bridge, not a permanent fix.
4
CRITICAL 9.2→CRITICAL 9.2
Hunt for indicators of compromise on all AhsayCBS hosts — Search for: unexpected .jsp files under %CBS_HOME%/webapps, the files Taskgmr.ps1, edge.exe, msedge.exe in temp directories, services named MicrosoftEdgeUpdateSvc, the kernel driver WinRing0x64.sys, and network connections to xmr.kryptex[.]network:8029 or imagefiles-backup.oss-ap-southeast-7.aliyuncs[.]com. If any IOCs are found, treat the host as fully compromised and begin incident response. Do this within the 3-day noisgate mitigation SLA window.
What doesn't work
  • Upgrading to AhsayCBS v10.3.4.0 does not help. Huntress independently confirmed this version remains vulnerable despite Ahsay initially claiming it addressed both CVEs. Only hotfix v10.3.4.45 and v9.15.2.70 are verified.
  • Network-level rate limiting or geo-blocking is insufficient. The exploit requires only a single HTTP request to bypass authentication — rate limiting has no meaningful effect, and the observed threat actors operate from diverse geographies.
  • Application-level logging alone does not prevent exploitation. AhsayCBS default logging may not capture the FromServlet parameter manipulation. By the time you detect it in logs, the webshell is already deployed.
04 · Intelligence Metadata

The supporting signals.

In-the-Wild ExploitationCONFIRMED ACTIVE. Huntress observed exploitation starting October 7, 2026 — 3 days after CVE publication. Five organizations compromised within 24 hours. Attackers deployed JSP webshells, XMRig cryptominers, and kernel drivers. Payloads staged from Alibaba Cloud (aliyuncs[.]com) infrastructure.
CISA KEV StatusAdded October 14, 2026 with a remediation deadline of October 17, 2026 (3-day window). This is among the most aggressive KEV deadlines CISA has issued, reflecting the severity and active exploitation.
Proof-of-ConceptPublic. Horizon3.ai released a full exploit chain PoC at github.com/horizon3ai/AhsayCBS-Auth-Bypass-RCE covering both CVE-2026-105133 (auth bypass) and CVE-2026-105134 (RCE). NIST noted released exploit code as early as October 4, 2026.
EPSS Score0.383% (31st percentile). The low EPSS score has not caught up with observed exploitation — EPSS is a lagging indicator here and should be disregarded in favor of KEV listing and confirmed incidents.
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L (7.3 HIGH). Network-attackable, no auth required, low complexity. The C:L/I:L/A:L impact reflects the auth bypass alone — not the chained RCE outcome. CVSS 4.0 per GHSA rates this 5.5 Moderate, further understating operational risk.
Affected VersionsAhsayCBS v7.x, v8.x, v9.x through 9.15.2, v10.x through 10.3.2. Version 10.3.4.0 (released Aug 4, 2026) was initially claimed as a fix but confirmed still vulnerable by Huntress.
Fixed Versionsv10.3.4.45 (for v10 line), v9.15.2.70 (for v9 line). v7/v8 users must upgrade to v9.15.0.0 first, then apply v9.15.2.70. Verified by Huntress as of October 12, 2026.
Reporting ResearcherHorizon3.ai Attack Team. Published full technical analysis and PoC. Huntress provided independent exploitation telemetry and incident response data.
Scanning/Exposure DataNo public Shodan/Censys enumeration count available for AhsayCBS specifically. However, AhsayCBS is widely deployed among MSPs who by design expose the management console to the internet for customer backup agent connectivity.
Companion CVECVE-2026-105134 (CVSS 10.0) — path traversal in the replication receiver file upload service enabling arbitrary JSP file write. Always chained with CVE-2026-105133 in observed attacks. Both must be patched together.

Sources.

  1. Horizon3.ai Technical Analysis
  2. SecurityWeek - AhsayCBS Exploited in the Wild
  3. CISA KEV Addition Alert (Oct 14, 2026)
  4. GitHub Advisory GHSA-fp2j-3cmp-828j
  5. Horizon3.ai PoC Repository
  6. Security.io - AhsayCBS Exploitation Reaches Backup Control Plane
  7. CyberUnit - AhsayCBS Zero-Day MSP Attack Analysis
  8. CISA Known Exploited Vulnerabilities Catalog
05 · The Call

Final Verdict
↑ UPGRADED to CRITICAL (9.2/10)

Why this verdict

  • Trivial unauthenticated exploitation: The auth bypass requires a single JSON parameter (FromServlet:Y) with no credentials, no user interaction, and low complexity. The public Horizon3.ai PoC automates the full chain. This is script-kiddie-grade exploitation with zero friction at the entry point.
  • Active exploitation with KEV listing: CISA added this to KEV on October 14, 2026 with a 3-day remediation deadline. Huntress confirmed five organizations breached starting October 7. This is not theoretical risk — it is happening now.
  • Role multiplier: AhsayCBS is canonically backup/DR infrastructure. By definition, 100% of AhsayCBS installations serve the backup control plane role. This is the high-value-role catalog entry for Backup/DR (alongside Veeam, Cohesity, Rubrik, Commvault). The documented chain (auth bypass → webshell → SYSTEM) succeeds in this role with blast radius extending to: (a) all backup data and encryption keys on the server, (b) stored credentials for every protected host, (c) in MSP deployments, every customer environment managed by the instance — a supply-chain-scale outcome. Per the floor rule, a canonical backup/DR component with a working chain to supply-chain compromise sets the verdict floor at CRITICAL.
  • Role multiplier: MSP supply-chain amplification. Ahsay markets AhsayCBS specifically to MSPs and system integrators as a white-label multi-tenant backup platform. A single compromised AhsayCBS instance in an MSP can provide access to hundreds of customer environments. This is not a workstation bug — it is a backup-infrastructure-as-supply-chain-pivot.
  • Broken patch situation compounds urgency. The initial vendor fix (v10.3.4.0, Aug 2026) was confirmed ineffective by Huntress. Verified hotfixes (v10.3.4.45, v9.15.2.70) were only available as of October 10-13 — meaning for over a week after active exploitation began, there was no working patch. Organizations that believed they were patched may still be vulnerable.

Why not higher?

A 9.2 rather than 10.0 reflects that CVE-2026-105133 alone provides auth bypass with limited direct impact (C:L/I:L/A:L); the catastrophic outcome requires chaining with CVE-2026-105134. While the chain is trivial and always observed together, they are separate CVEs and the full CVSS 10.0 impact belongs to the companion vulnerability. Additionally, AhsayCBS is a niche product compared to Veeam or Commvault — the total exposed population is smaller, though concentration in MSPs amplifies per-instance impact.

Why not lower?

Downgrading below CRITICAL is impossible given the deployment-role floor. AhsayCBS is canonically backup/DR infrastructure with supply-chain blast radius in MSP deployments. The chain is trivially exploitable, publicly documented, and actively being used in the wild. CISA’s 3-day KEV deadline independently validates CRITICAL urgency. The auth bypass is the key that unlocks the entire chain — treating it as merely HIGH ignores that without CVE-2026-105133, CVE-2026-105134 is unreachable.

06 · Verification

Crowdsourced verification payload.

Run this script from any auditor workstation or CI runner that has network access to the AhsayCBS management interface. It requires curl and jq. Invoke with: bash check_ahsaycbs_cve2026105133.sh https://your-ahsaycbs-host:443. No special privileges required on the auditor machine — it only sends HTTP requests to the target.

noisgate-verify.sh
BASHREAD-ONLYSAFE
#!/usr/bin/env bash
# check_ahsaycbs_cve2026105133.sh
# Checks AhsayCBS for CVE-2026-105133 (Authentication Bypass)
# Usage: bash check_ahsaycbs_cve2026105133.sh <BASE_URL>
# Exit codes: 1=VULNERABLE, 0=PATCHED, 2=UNKNOWN

set -euo pipefail

if [ $# -lt 1 ]; then
  echo "Usage: $0 <BASE_URL>"
  echo "Example: $0 https://backup.example.com:443"
  exit 2
fi

BASE_URL="${1%/}"
API_PATH="/obs/api/ApiStructsAction"
TARGET="${BASE_URL}${API_PATH}"

echo "[*] Testing AhsayCBS at: ${TARGET}"
echo "[*] Sending auth bypass probe (FromServlet:Y)..."

# Attempt the auth bypass - send a request with FromServlet:Y
# If the server responds with authenticated API data instead of 401/403, it is vulnerable
RESPONSE=$(curl -sk -o /dev/null -w "%{http_code}" \
  -X POST "${TARGET}" \
  -H "Content-Type: application/json" \
  -d '{"AhsayOBM":true,"FromServlet":"Y","action":"getServerSetting"}' \
  --connect-timeout 10 --max-time 15 2>/dev/null) || true

if [ -z "$RESPONSE" ]; then
  echo "[!] UNKNOWN - Could not connect to ${TARGET}"
  echo "    Verify the URL and port are correct."
  exit 2
fi

echo "[*] HTTP response code: ${RESPONSE}"

# Also check the version endpoint if available
VERSION_RESP=$(curl -sk "${BASE_URL}/obs/api/version" --connect-timeout 10 --max-time 10 2>/dev/null) || true

if echo "$VERSION_RESP" | grep -qiE '(10\.3\.[0-2]|10\.[0-2]\.|9\.1[0-4]\.|9\.15\.[0-1]\.|9\.15\.2\.[0-6][0-9]$|[78]\.)'; then
  echo "[*] Detected potentially vulnerable version string in response."
  VERSION_VULN=true
else
  VERSION_VULN=false
fi

if [ "$RESPONSE" = "200" ]; then
  echo ""
  echo "========================================"
  echo "  RESULT: VULNERABLE"
  echo "========================================"
  echo "  The AhsayCBS instance accepted an unauthenticated"
  echo "  API request with the FromServlet bypass."
  echo "  CVE-2026-105133 is exploitable."
  echo "  ACTION: Apply hotfix v10.3.4.45 or v9.15.2.70 IMMEDIATELY."
  echo "  ACTION: Restrict management interface to trusted IPs/VPN."
  echo "  ACTION: Hunt for IOCs (JSP webshells, Taskgmr.ps1, msedge.exe)."
  exit 1
elif [ "$RESPONSE" = "401" ] || [ "$RESPONSE" = "403" ]; then
  if [ "$VERSION_VULN" = true ]; then
    echo ""
    echo "========================================"
    echo "  RESULT: UNKNOWN (version may be vulnerable)"
    echo "========================================"
    echo "  Auth bypass probe was rejected, but version"
    echo "  string suggests an unpatched release."
    echo "  Verify hotfix v10.3.4.45 or v9.15.2.70 is installed."
    exit 2
  else
    echo ""
    echo "========================================"
    echo "  RESULT: PATCHED"
    echo "========================================"
    echo "  The AhsayCBS instance rejected the unauthenticated"
    echo "  API request. The auth bypass does not appear exploitable."
    exit 0
  fi
else
  echo ""
  echo "========================================"
  echo "  RESULT: UNKNOWN"
  echo "========================================"
  echo "  Unexpected HTTP response code: ${RESPONSE}"
  echo "  Manual verification required."
  exit 2
fi