How to Patch Aspera Faspex 5 and Audit Admin Accounts
How to patch Aspera Faspex 5 for CVE-2026-123218, verify the faspex-core version, and audit admin accounts for signs of compromise after the fix.
To patch Aspera Faspex 5 for CVE-2026-123218, run IBM's container image patch procedure as root, confirm that the faspex-core image reports 5.0.19 with commit 1ce4b13 and Fix Pack 1, and then audit every administrator account on the server. Patching alone is not enough here: CISA lists the flaw as exploited, so a server that was exposed before the fix may already have a rogue admin. This guide covers inventory, patch, verification and the account review.
The background is in our news coverage of the Aspera Faspex CVE-2026-123218 exploitation. In short: IBM fixed an authorization bypass in Faspex 5.0.0 through 5.0.19 on 7 November 2026, CISA added it to the KEV catalog on 9 November, and there is no workaround.
Which Aspera Faspex versions need the patch?
Faspex 5.0.0 through 5.0.19 on Linux are affected, according to IBM's bulletin. The fixed release is 5.0.19 PL1.
The bulletin covers Faspex 5 only. Confirm which version each server runs before you plan the work.
Step 1: Inventory every Faspex server
Start with a list. Check:
- DNS records and certificates that mention Faspex or Aspera
- Firewall rules that publish file transfer ports or web interfaces
- Cloud accounts and virtualization hosts for servers built by project teams
- Disaster recovery and staging copies, which often lag production on patches
Record for each server: owner, internet exposure, version and whether external users can log in. Exposed servers with external users go first.
Step 2: Plan a short maintenance window
Patching restarts the Faspex containers, so transfers in progress will stop. Tell the business owners and partner contacts. Take a snapshot or backup per your normal change process before you start. IBM's version output lists MariaDB and Nginx alongside the Faspex images, so the database is part of the stack you are restarting.
How do you patch Aspera Faspex 5 container images?
You patch Faspex 5 by running IBM's setup command as root, which pulls the updated images for the same tag. IBM's documentation says this does not require upgrading the Faspex 5 RPM.
The command from IBM's patching guide:
faspexctl setup
Follow the prompts IBM's tool presents. If the server cannot reach the image registry, work with IBM support on an offline image transfer; do not leave the server unpatched while you sort it out.
How do you verify the Faspex patch is applied?
Run IBM's version command and check the faspex-core line. The bulletin says it must show 5.0.19 with commit 1ce4b13 and Fix Pack 1.
faspexctl version
The output lists each container image with its version and commit hash. Save the output in the change ticket. If faspex-core still shows an earlier build, the patch did not apply; do not close the change.
Step 3: Audit administrator accounts
This is the step that catches an attacker who got in before you patched. The bypass grants full administrative privileges, so the most likely trace is an account with more rights than it should have.
- Export the user list from the Faspex admin interface, including each user's role and creation date.
- Compare admins against your records. Every admin should map to a named person and an approved request. Anyone you cannot match is suspect.
- Check recent role changes. A normal user promoted to admin is as serious as a brand new admin account.
- Review accounts created since late October. IBM published on 7 November and the attack timeline is not public, so cast a wide net.
- Look at API credentials and integrations. An attacker with admin rights may add credentials that survive a password reset.
Do not delete suspicious accounts until you have saved logs. Disable them first, then collect evidence.
Step 4: Check what an attacker could have touched
If you find an account you cannot explain, treat the server as compromised:
- Review package downloads and shares since the account appeared.
- Check changes to authentication settings, such as directory or single sign-on configuration.
- Check changes to storage connections and email or notification settings.
- Rotate every credential the server stores, including directory bind accounts and storage keys.
- Notify partners whose files sat on the server, following your incident response plan.
CISA flagged this KEV entry for forensic triage under BOD 26-04, which signals that federal agencies are expected to look for compromise rather than just patch.
Step 5: Reduce exposure going forward
- Restrict the admin interface to internal networks where the product allows it.
- Turn off self-registration if the business does not need it.
- Expire external accounts after each project.
- Send admin creation and role change events to your SIEM with an alert.
Understanding the bug class helps when the next bulletin lands. Our explainer on what incorrect authorization (CWE-863) means covers it. For the planning view, see why file transfer servers get exploited.