CVE-2026-123218: IBM Aspera Faspex Broken Authorization to Remote Administrative Takeover
IBM Aspera Faspex 5.x enterprise high-speed file exchange software contains an unauthenticated authorization bypass flaw (CVE-2026-123218, CVSS 9.8) added to the CISA Known Exploited Vulnerabilities (KEV) catalog on November 9, 2026. A breakdown in API route middleware validation allows remote attackers to access privileged endpoints without authentication tokens. Attackers invoke '/api/v5/users' to silently provision new administrator credentials, granting them full dominion over the file transfer platform. Threat actors leverage this access to intercept and exfiltrate proprietary intellectual property, financial records, and medical files passing through high-speed WAN transfers. Upgrading to IBM Aspera Faspex 5.0.19 Patch Level 1 (PL1) is critically required.
HERMES THREAT SCORE & ENTERPRISE RISK EVALUATION
Target:IBM Aspera Faspex Core API Routing and User Management Dispatch Engine Hermes assigns an HTS score of 97 (CRITICAL), fully matching the CVSS 9.8 rating. Aspera Faspex is deployed on boundary infrastructure specifically to handle bulk, high-value data exchanges across enterprise perimeters. Exploitation bypasses multi-factor authentication, immediately exfiltrating Petabytes of sensitive data without requiring client-side interaction or endpoint malware deployment.
1. Executive Summary & Operational Context
Section titled โ1. Executive Summary & Operational ContextโIBM Aspera Faspex is an enterprise-scale file exchange, sharing, and synchronization platform leveraging Asperaโs proprietary FASP protocol to transfer large datasets across global WAN environments at multi-gigabit speeds.
On November 9, 2026, CISA cataloged CVE-2026-123218 following confirmed active exploitation against corporate Faspex deployments. Attackers bypass API authorization guards to create rogue administrator accounts, exfiltrate sensitive datasets, and abuse pre/post-transfer script execution hooks to gain interactive root shell access on the host.
2. Technical Vulnerability Analysis & Root Cause
Section titled โ2. Technical Vulnerability Analysis & Root CauseโThe vulnerability stems from an inconsistency in the routing authentication middleware of Faspex 5.x. When incoming HTTP requests are handled by the reverse proxy and forwarded to internal Node.js/Ruby microservices, internal route normalization fails on specific URI variants:
// Vulnerable middleware snippet in Faspex route handlerfunction verifyAuthToken(req, res, next) { // Flawed path matching allowing bypass via URL case sensitivity or trailing slashes if (req.path.startsWith('/api/v5/public') || req.path.toLowerCase().includes('/setup/')) { return next(); // Bypasses token verification } // Expected authorization verification const token = req.headers['authorization']; if (!token) return res.status(401).json({ error: "Unauthorized" }); // ...}By requesting paths such as /api/v5/public/../users or utilizing specific HTTP header overrides (X-Original-URL: /api/v5/users), unauthenticated attackers bypass the token check entirely. The user controller accepts the POST request and creates an account with role: "admin":
{ "name": "backup_service", "email": "attacker@c2-domain.com", "password": "Password123!", "role": "admin", "status": "active"}3. Attack Execution Flow & Weaponization Mechanics
Section titled โ3. Attack Execution Flow & Weaponization Mechanicsโflowchart TD A["Remote Adversary (Internet)"] -->|"Step 1: POST /api/v5/public/../users<br/>(Bypasses Auth Middleware)"| B["IBM Aspera Faspex API<br/>(Ports 443 / 8443)"] B -->|"Creates Rogue Admin Account"| C["Admin Account: backup_service"] C -->|"Step 2: Logs in via GUI / REST API"| D["Administrative Dashboard"] D -->|"Step 3: Accesses All File Packages & Encrypted Assets"| E["Enterprise Transfer Repositories"] D -->|"Step 4: Configures Transfer Notification Webhook<br/>with Shell Script Payload"| F["Faspex Service Host (Linux)"] F -->|"Executes Arbitrary Code as root"| G["Persistent Reverse Shell Established"]4. Forensic Signatures, Detection Queries & IOCs
Section titled โ4. Forensic Signatures, Detection Queries & IOCsโSigma Detection Rule
Section titled โSigma Detection Ruleโtitle: IBM Aspera Faspex Unauthenticated Admin Creation Attemptid: 3a91b412-1232-4d99-a108-f81d12321801status: experimentaldescription: Detects path traversal and unauthorized user creation on IBM Aspera Faspex APIlogsource: category: webserverdetection: selection: cs-method: 'POST' cs-uri-stem|contains: - '/api/v5/' - '/users' cs-uri-stem|contains|any: - '..' - 'public/..' condition: selectionlevel: criticalThreat Intelligence & Indicators of Compromise (IOCs)
Section titled โThreat Intelligence & Indicators of Compromise (IOCs)โ| Type | Indicator | Context |
|---|---|---|
| IP Address | 194.26.29[.]99 | Exploit delivery and API probing IP |
| IP Address | 185.220.101[.]15 | C2 staging host capturing exfiltrated file archives |
| IP Address | 91.240.118[.]201 | Scanner source validating Faspex versions |
| Log Entry | POST /api/v5/users 201 Created | Abnormal user creation event in web logs |
| Account Name | backup_service, aspera_admin | Rogue administrative accounts created by exploit |
5. Comprehensive Remediation, Hardening & Mitigation Plan
Section titled โ5. Comprehensive Remediation, Hardening & Mitigation Planโ-
Apply IBM Security Patch Immediately: Upgrade all IBM Aspera Faspex 5.x instances to version 5.0.19 Patch Level 1 (PL1) or later.
-
Audit User Accounts and Admin Roles: Review the Faspex user database (
GET /api/v5/usersor via web UI). Inspect all accounts created or modified within the past 60 days, especially those possessing administrator or package management privileges. -
Restrict Network Ingress: Place Faspex administrative endpoints behind a Web Application Firewall (WAF) or VPN gateway. Block external access to paths containing
/api/v5/adminand/api/v5/users. -
Inspect Automated Post-Transfer Hooks: Review all configured pre- and post-processing scripts in the Faspex transfer engine. Delete any unrecognized bash, Python, or batch scripts configured to execute on package receipt.