IBM Aspera Faspex Vulnerability: Fix Is 5.0.19 PL1

IBM Aspera Faspex vulnerability CVE-2026-123218: authorization bypass to full administrator, CISA KEV, fixed in 5.0.19 PL1, November 2026

An IBM Aspera Faspex vulnerability, CVE-2026-123218, is being exploited and sits in CISA’s list of exploited vulnerabilities. A crafted message lets a Faspex 5 user bypass authorization and gain full administrator privileges (CVSS 9.8). IBM’s fix is 5.0.19 PL1, and the CISA deadline for US federal agencies was November 12.

What Happened With the IBM Aspera Faspex Vulnerability

IBM’s bulletin, dated November 7, describes an incorrect-authorization flaw in Aspera Faspex 5. Per IBM, an authenticated user can craft a specific message to bypass authorization and gain full administrative privileges. Versions 5.0.0 through 5.0.19 are affected. IBM scores it CVSS 9.8, with a vector that means network access, low complexity, no privileges and no user interaction. As of November 16, IBM lists no workaround.

The fix is Faspex 5.0.19 PL1 for Linux, applied by patching the container images. IBM tells customers to confirm afterwards that the faspex-core container image shows 5.0.19 (1ce4b13, Fix Pack 1).

CISA added the flaw to its Known Exploited Vulnerabilities catalog on November 9, on evidence of active exploitation, and set November 12 as the deadline for US federal agencies. The same alert added GPUStack, SignalWire FreeSwitch and OpenSSH flaws. IBM’s bulletin does not mention exploitation. As of November 16, the sources we read give no details on the attacks, no attacker and no victims; SecurityWeek reported the same on November 10.

Why It Matters

A file-transfer portal sits between your company and its partners. An administrator on it controls users, transfers and the connections to the storage behind it. Assumption: Faspex is used mostly in media, life sciences and large enterprises that move very large files; we have no data on how common it is in German mid-market companies.

One detail does not add up. IBM’s summary speaks of an authenticated user, yet its CVSS vector says no privileges are required. IBM has not said which is right, so plan for the worse case: a Faspex reachable from the internet may be exposed without a login. For pharma and finance firms that exchange batch data, clinical files or reports, an unnoticed administrator is a GDPR and NIS2 problem, not only an IT one. The need to check the actual container image reminds us of our Zyxel GS1900 post: a patch is only real once you have verified the build that runs.

What You Should Do Now

  1. Find every Faspex 5 instance, including forgotten test systems and ones run by other departments. Upgrade to 5.0.19 PL1 following IBM’s container patching instructions, then confirm that the faspex-core image shows 5.0.19 with Fix Pack 1.
  2. Until the patch is in, limit access to Faspex to known networks or your VPN. This is our recommendation; as of November 16, IBM lists no workaround.
  3. Review the administrator list and recent role changes. Look for admin accounts nobody can explain, going back as far as your logs allow. CISA gives no start date for the exploitation.
  4. If you find unexplained admin changes, treat the system as compromised: review transfer activity and downloads, and rotate the credentials Faspex holds for storage and email (Assumption: Faspex stores such credentials).

DIESEC Perspective

CISA’s three-day deadline for this flaw tells you how it ranks the risk. A transfer portal holds access to data that belongs to other systems and other companies, and whoever controls it reaches that data. Ask two questions this week: who can reach Faspex from the internet, and who watches its admin list?

Not sure whether your file-transfer platform runs the patched image? Contact DIESEC for a rapid patch verification and privileged-account review.

Sources: IBM | CISA | SecurityWeek
Published: 2026-11-18 | Category: Vulnerabilities & Patches | ~4 min read