IBM Aspera Faspex CVE-2026-123218 Exploited, Added to KEV
Security

IBM Aspera Faspex CVE-2026-123218 Exploited, Added to KEV

Aspera Faspex CVE-2026-123218 lets a logged-in user become admin on Faspex 5.0.0 to 5.0.19. It is exploited and on CISA KEV. Patch to 5.0.19 PL1 now.

ibm aspera faspexauthorization bypasscisa kevfile transfer

IBM Aspera Faspex CVE-2026-123218 is an authorization bypass that lets a logged-in user gain full administrative privileges on Faspex 5.0.0 through 5.0.19. IBM fixed it in 5.0.19 PL1 on 7 November 2026, and CISA added it to the Known Exploited Vulnerabilities catalog on 9 November with a 12 November deadline. If you run Faspex 5 on Linux, patch the container images now, confirm the faspex-core version, then review every administrator account.

What happened

IBM published a security bulletin on 7 November 2026 for CVE-2026-123218 in Aspera Faspex, its file exchange server for moving large files between organizations. The bulletin says an authorized user can craft a specific message to bypass user authorization and gain full administrative privileges. The weakness is classified as CWE-863, incorrect authorization.

Two days later, on 9 November, CISA added the flaw to its KEV catalog. That listing means CISA has evidence of exploitation in real attacks. The federal remediation deadline was 12 November, three days after the listing, and CISA marked the entry for forensic triage under BOD 26-04. That means agencies are expected to look for signs of compromise, not only install the fix.

IBM's bulletin does not mention exploitation, and SecurityWeek reported on 10 November that no details about the attacks appear to be public. CISA lists known ransomware use as "Unknown".

Who is affected

The bulletin lists these versions:

  • Affected: IBM Aspera Faspex 5.0.0 through 5.0.19 on Linux
  • Fixed: IBM Aspera Faspex 5.0.19 PL1
  • Workarounds: none. IBM says to upgrade.

IBM gives one check for a patched system: the faspex-core container image should report 5.0.19 (1ce4b13, Fix Pack: 1).

Faspex servers usually face the internet, because their job is to exchange files with partners, customers and production vendors. Many organizations also allow self-registration or invite external users. Any account that can log in is a possible starting point for this bug, so external user populations widen the exposure.

How Aspera Faspex CVE-2026-123218 works

IBM has not published the message format or the code path involved, and nothing in this article describes one. What the public record does establish:

  • The flaw is an authorization failure, not an authentication failure. The server knows who the user is but grants that user actions reserved for administrators. Our explainer on incorrect authorization (CWE-863) covers how this class of bug works and why it is easy to miss in testing.
  • IBM scored it CVSS 3.1 9.8 with the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The PR:N part says no privileges are required, while the description says an "authorized user" can exploit it. Those two statements disagree. Treat the flaw as reachable by anyone who can obtain or create a Faspex login, and do not lower the priority because the description mentions authentication. We covered this pattern in why vendor severity and CVSS scores disagree.
  • Full administrative control of a file exchange server means access to stored packages, user accounts, and the server's configuration, including its links to other systems.

This is not the first exploited Faspex flaw. CVE-2022-47986, a YAML deserialization bug in Faspex, was added to the KEV catalog on 21 February 2023 and is marked as used in ransomware campaigns. That older bug is a separate issue and says nothing direct about who is exploiting CVE-2026-123218. It does show that attackers already know this product and look for exposed instances.

What to do now

  1. Find every Faspex 5 instance. Include test, staging and disaster recovery servers. File exchange servers are often set up for one project and forgotten.
  2. Patch the container images. IBM's documentation for patching Faspex 5 container images says to run the setup command as root. New images are pushed to the same tag, so the Faspex 5 RPM does not need an upgrade:
faspexctl setup
  1. Verify the version. IBM's documentation uses this command to list each container image with its version and commit hash:
faspexctl version

Confirm that faspex-core reports 5.0.19 with commit 1ce4b13 and Fix Pack 1, as the bulletin specifies. Our step-by-step guide on how to patch Aspera Faspex 5 and audit admin accounts walks through the full sequence, including the review afterwards.

  1. If you cannot patch today, cut exposure. IBM lists no workaround. Restricting the web interface to known partner IP ranges or a VPN shrinks the set of people who can try the bug. It does not fix it.
  2. Assume compromise on exposed servers until checked. CISA asked for forensic triage, and exploitation started before or around the fix. On every instance that was reachable from the internet and ran 5.0.19 or earlier:
  • Compare the administrator list against your records and remove any admin you cannot account for.
  • Look for new users, new API credentials, changed authentication settings and changed external connections.
  • Review which packages were downloaded or shared, and by whom, since the patch window opened.
  • Rotate credentials stored on the server, such as service accounts used to connect to storage or directories.
  1. Preserve logs before you clean up. If you find an unexplained admin account, copy server and proxy logs first, then remove the account.

What to watch next

  • An IBM bulletin update. The current bulletin has no acknowledgement and no exploitation note. A revision could add indicators or a corrected CVSS vector.
  • Attack details from CISA or a researcher. Without them, defenders can only hunt for outcomes (new admins, changed settings), not the exploit itself.
  • Ransomware attribution. The KEV entry currently says "Unknown". File transfer servers have a history of being used for data theft and extortion; our piece on why file transfer servers get exploited explains why, and how to plan for the next one.

The Kiteworks precautionary shutdown in September is another recent example of a file sharing product pulled into an urgent response.

Sources