NVD published CVE-2026-123218 on November 7, 2026. Two days later, on November 9, CISA added it to the KEV catalog with a due date of November 12.
IBM Aspera Faspex is IBM's large-file exchange platform: organizations use it to send video, datasets and bulky deliverables to outside partners. By design, then, it is reachable from the Internet and full of files their owners specifically didn't want to hand to a consumer service.
The vulnerability
| Field | Value |
|---|---|
| CVE | CVE-2026-123218 |
| CVSS 3.1 (IBM, CNA) | 9.8 (CRITICAL) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Type | Incorrect authorization (CWE-863) |
| NVD status | Undergoing Analysis |
| Affected versions | 5.0.0 through 5.0.19 |
| NVD published | 2026-11-07 |
| Added to CISA KEV | 2026-11-09 |
| CISA due date | 2026-11-12 |
Per NVD, an authorized user can craft a specific message to bypass authorization checks and gain full administrative privileges.
The score is IBM's, as CNA. NVD hasn't finished its analysis and publishes neither its own score nor a CPE configuration yet.
A vector that doesn't quite match the description
Both the NVD description and the KEV entry talk about an authorized or authenticated user. Yet IBM's vector says PR:N — no privileges required. The public data allows two readings, and doesn't settle which one is right:
- the score slightly overstates the flaw, and an account really is needed;
- or the "account" is easy to come by — on a file-exchange platform, guest or external accounts get created for every partner.
In the second case, the line between "authenticated" and "unauthenticated" is thin: an outside Faspex recipient is a user.
What "full admin" means on a file-exchange platform
The administrator of a file-exchange platform manages accounts, permissions and configuration — in practice, control over everything that moves through it, not just one user's files. That is what makes escalating to that role as serious as direct access to the data.
CISA doesn't describe the exploitation campaign, and lists ransomware use as "Unknown".
Affected versions
| Product | Affected versions (NVD description) |
|---|---|
| IBM Aspera Faspex 5 | 5.0.0 through 5.0.19 inclusive |
NVD gives no fixed version. The referenced IBM advisory (ibm.com/support/pages/node/7295921) states which version or fix to apply: check it before treating any version as safe.
The installed version is shown in the Faspex admin interface and in the metadata of the deployed package or image.
Detection
- Administrator accounts that are new, or demoted then promoted; role changes with no matching ticket
- Package access by accounts that weren't recipients
- Configuration changes: storage, SMTP relay, integrations, authentication
- Guest or external accounts active from unusual IP addresses
- Abnormal outbound download volumes
CISA requires forensic triage (BOD 26-04) on top of patching.
Mitigation
1. Apply IBM's fix
Per the IBM advisory above. The CISA deadline is November 12.
2. Shrink the attack surface in the meantime
- Restrict the admin interface to internal addresses
- Disable or expire unused guest and external accounts
- Pause self-registration if it is enabled
3. After patching
- Review the administrator list and role assignments
- Rotate privileged account credentials and integration secrets (storage, SMTP, directory)
- Identify packages accessed during the exposure window: if third-party files leaked, notification duties may apply, notably under GDPR
It's the second time in a matter of days that an IBM product has piled up critical flaws, after the 35 IBM API Connect CVEs.
Why continuous monitoring of your file-transfer platforms matters
File-transfer platforms are a recurring target: exposed by nature, and full of valuable data. A KEV entry with a three-day deadline leaves no time to go hunting for which version is running.
With cveo.tech, inventory your Internet-facing applications with their exact versions, and get an alert as soon as a CVE affecting them lands in the CISA KEV catalog.