CVE-2026-123218 - IBM Aspera Faspex Incorrect Authorization Vulnerability

CVE-2026-123218

IBM Aspera Faspex 5 - Authorization Bypass to Full Administrative Control via a Crafted Message

What is IBM Aspera Faspex?

IBM Aspera Faspex is a managed file exchange application built on Aspera's FASP protocol, which moves very large files over long-haul networks far faster than TCP-based transfers can. Faspex puts a web front end on top of it: users send and receive "packages" through a browser or email-style workflow, administrators set quotas and retention, and the whole thing integrates with corporate directories. It is the standard tool in media and entertainment for moving finished video between facilities, and it is widely used in life sciences, government, and any industry that routinely ships terabyte-scale datasets between organizations.

Managed file transfer platforms are among the most consistently attacked classes of enterprise software, and for good reason. They are internet-facing by requirement, because external partners have to reach them. They hold, by design, a concentrated store of whatever an organization considers worth sending securely. And administrative control over one is effectively a data-exfiltration tool the victim has already provisioned and trusted. The industry's recent history, from MOVEit Transfer to GoAnywhere MFT to Cleo, is largely a history of extortion groups working through this exact category.

Faspex itself carries that history. CVE-2022-47986, a pre-authentication YAML deserialization flaw in Faspex 4.4.2 Patch Level 1 and earlier, was added to the KEV catalog on 2023-02-21 and exploited by at least two ransomware operations, IceFire and Buhti, with IceFire using it specifically to land a Linux ransomware variant on CentOS-based Faspex servers.

Overview

CVE-2026-123218 is an authorization bypass in IBM Aspera Faspex 5. Per IBM's bulletin, a user can craft a specific message that bypasses the application's authorization checks and escalates privileges, with successful exploitation yielding full administrative control of the Faspex instance. IBM rates it 9.8 CRITICAL under CVSS 3.1 with the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, and classifies it as CWE-863, incorrect authorization.

IBM published security bulletin 7295921 on 2026-11-07, the same day the CVE record went public, and the identifier had been reserved two days earlier. Two days after that, on 2026-11-09, CISA added the CVE to the Known Exploited Vulnerabilities catalog in an alert covering four additions, all made "based on evidence of active exploitation," with a BOD 26-04 remediation deadline of 2026-11-12.

Be aware that several third-party vulnerability trackers still describe this CVE as not known to be exploited and not in KEV. Those records predate the 2026-11-09 catalog addition and are stale rather than contradictory; CISA's own alert is the authoritative statement. IBM's bulletin itself makes no claim about exploitation either way.

Affected Versions

Product Vulnerable Fixed
IBM Aspera Faspex 5 (Linux) 5.0.0 through 5.0.19 5.0.19 Patch Level 1 (PL1)
IBM Aspera Faspex 5 (container deployment) faspex-core image older than the fix pack build faspex-core image reading 5.0.19 (1ce4b13, Fix Pack: 1)

IBM lists no affected versions outside the 5.x line in this bulletin. Faspex 4.x reached end of support before this record and is not addressed by the fix pack.

Technical Details

The weakness is CWE-863, incorrect authorization. In plain words, the application does perform an authorization check, but the check reaches the wrong conclusion for certain inputs: a request that should be rejected as outside the caller's privileges is accepted and performed. This is distinct from a missing check (CWE-862) and from an authentication bypass; the request is evaluated, and the evaluation is wrong.

IBM's description centres on a crafted "message." Faspex's package and messaging workflow is the application's primary user-facing feature, so the plausible reading is that a field in a user-submitted message or package object influences the privilege decision applied to the resulting operation. IBM has not published the vulnerable endpoint, the offending field, or any proof-of-concept detail, and no independent technical write-up existed as of 2026-11-09. Treat the mechanism as unconfirmed.

Sources conflict on whether an attacker needs an account. IBM's prose says an "authorized user" crafts the message, which implies a valid, low-privilege Faspex account as the precondition. But IBM's own CVSS vector sets Privileges Required to None, which implies no account at all. These cannot both be right. Plan on the weaker assumption, that no account is needed, because that is what the vendor's machine-readable score asserts and because Faspex deployments frequently allow self-registration or hold a large population of external partner accounts, which makes "authenticated" a low bar in practice either way.

Discovery

IBM's bulletin includes an acknowledgement section but names no researcher, reporting party, or coordinating organization. No external party had publicly claimed the finding as of 2026-11-09.

The compressed sequence is itself informative. The identifier was reserved on 2026-11-05, the bulletin and CVE record were published together on 2026-11-07, and CISA listed the CVE for active exploitation on 2026-11-09, four days from reservation to KEV. That pattern, with no coordinated-disclosure window and no credited researcher, is characteristic of a flaw surfaced through incident response on a live intrusion rather than one reported by a researcher and fixed on a schedule.

Exploitation Context

CISA states the vulnerability is being actively exploited; that is the entirety of the public evidence. No threat actor, campaign, victim count, or indicator set has been attributed, no proof-of-concept is public, and CISA has not marked the entry for known ransomware use. Note that the ransomware flag reflects what has been confirmed so far, not a prediction, and the prior Faspex KEV entry did carry it.

No exposure census from Shadowserver, Censys, or GreyNoise had been published as of 2026-11-09. Faspex instances are internet-facing by function, so the exposed population is effectively the deployed population.

The realistic threat model follows the managed-file-transfer pattern rather than a commodity-botnet one: a small number of operators work through reachable instances quickly, take administrative control, and exfiltrate stored packages for extortion, often without deploying an encryptor at all. The three-day KEV deadline, unusually short even under BOD 26-04, is consistent with CISA viewing this as that kind of event.

Remediation

  1. Upgrade to IBM Aspera Faspex 5.0.19 Patch Level 1 on Linux. IBM lists no workarounds and no mitigations, so patching is the only remedy the vendor offers.
  2. For container deployments, confirm the running faspex-core image reports version 5.0.19 (1ce4b13, Fix Pack: 1) after the upgrade. Verify the running image rather than the deployment manifest, since a cached or pinned tag can leave the old build in service.
  3. Until the fix pack is applied, restrict network reachability. Put the Faspex web interface behind a VPN or an authenticating reverse proxy, or allowlist partner source networks. This does not fix the flaw, but it removes the opportunistic attacker.
  4. Audit Faspex accounts and privileges now, not after the upgrade. Disable self-registration if it is enabled, review the administrator list for accounts nobody created, and remove dormant external partner accounts. If the precondition really is a low-privilege account, this is the control that matters most.
  5. Assume compromise on any instance that was internet-reachable and unpatched. Review package transfer logs for bulk downloads of packages by a single account, for administrative actions taken outside normal hours, and for new API keys or integration credentials. Preserve logs and system state before remediating, in line with CISA's Forensics Triage Requirements under BOD 26-04.
  6. Rotate Faspex administrative credentials, any directory service account bound to Faspex, and any transfer-node or storage credentials the server holds.
  7. Federal civilian agencies must remediate or discontinue use by 2026-11-12. The deadline is three days from listing, which is short even by BOD 26-04 standards. Non-federal operators of an internet-facing Faspex instance should treat it the same way.

Key Details

PropertyValue
CVE ID CVE-2026-123218
Vendor / Product IBM - Aspera Faspex
NVD Published2026-11-07
NVD Last Modified2026-11-07
CVSS 3.1 Score9.8
CVSS 3.1 VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
SeverityCRITICAL
CWE CWE-863 find similar ↗
CISA KEV Added2026-11-09
CISA KEV Deadline2026-11-12
Known Ransomware Use No

CVSS 3.1 Breakdown

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Required Action

CISA BOD 26-04 Deadline: 2026-11-12. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA's BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA's "Forensics Triage Requirements" (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Timeline

DateEvent
2026-11-05CVE-2026-123218 reserved
2026-11-07IBM publishes security bulletin 7295921 and the fix in 5.0.19 PL1
2026-11-07CVE record published with an IBM-assigned CVSS 3.1 base score of 9.8
2026-11-09Added to CISA Known Exploited Vulnerabilities catalog based on evidence of active exploitation
2026-11-12CISA BOD 26-04 remediation deadline