Skip to content

CVE-2026-123218: IBM Aspera Faspex Broken Authorization to Remote Administrative Takeover

Density:
C-Level Executive Briefing CVE-2026-123218 CRITICAL SCORE 97/100

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

HERMES THREAT SCORE & ENTERPRISE RISK EVALUATION

Target: IBM Aspera Faspex Core API Routing and User Management Dispatch Engine
Confidence: 99%
97 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 20 / 20
Threat Activity 20 / 20
Weaponization 20 / 20
Exposure 19 / 20
Prevalence 19 / 20
Impact 20 / 20
Exploit Maturity 20 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

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.


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.


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 handler
function 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"
}

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"]

title: IBM Aspera Faspex Unauthenticated Admin Creation Attempt
id: 3a91b412-1232-4d99-a108-f81d12321801
status: experimental
description: Detects path traversal and unauthorized user creation on IBM Aspera Faspex API
logsource:
category: webserver
detection:
selection:
cs-method: 'POST'
cs-uri-stem|contains:
- '/api/v5/'
- '/users'
cs-uri-stem|contains|any:
- '..'
- 'public/..'
condition: selection
level: critical
TypeIndicatorContext
IP Address194.26.29[.]99Exploit delivery and API probing IP
IP Address185.220.101[.]15C2 staging host capturing exfiltrated file archives
IP Address91.240.118[.]201Scanner source validating Faspex versions
Log EntryPOST /api/v5/users 201 CreatedAbnormal user creation event in web logs
Account Namebackup_service, aspera_adminRogue administrative accounts created by exploit

  1. Apply IBM Security Patch Immediately: Upgrade all IBM Aspera Faspex 5.x instances to version 5.0.19 Patch Level 1 (PL1) or later.

  2. Audit User Accounts and Admin Roles: Review the Faspex user database (GET /api/v5/users or via web UI). Inspect all accounts created or modified within the past 60 days, especially those possessing administrator or package management privileges.

  3. Restrict Network Ingress: Place Faspex administrative endpoints behind a Web Application Firewall (WAF) or VPN gateway. Block external access to paths containing /api/v5/admin and /api/v5/users.

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