IBM published a fix for a critical flaw in its Aspera Faspex file-transfer server on Nov. 7. Two days later the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added the bug to its Known Exploited Vulnerabilities (KEV) catalog. That means CISA has evidence someone is already using it against real systems. Federal civilian agencies got a three-day deadline, and CISA marked the entry for forensic triage.
The bug is tracked as CVE-2026-123218. It affects IBM Aspera Faspex 5.0.0 through 5.0.19. IBM scores it 9.8 out of 10 on CVSS 3.1, which puts it in the critical band. The fix is Faspex 5.0.19 PL1. IBM lists no workarounds.
What the flaw does
Aspera Faspex is IBM's file-transfer product for sending large files between people and organizations. Servers that exchange files with outside partners are often reachable from the internet, which is one reason a flaw like this deserves attention.
IBM's security bulletin says the flaw lets an authorized user "craft a specific message to bypass user authorization and gain full administrative privileges." The CVE.org record carries the same wording. IBM classifies it as CWE-863, Incorrect Authorization. In plain terms, the server checks who you are but does not properly check what you are allowed to do. With the right request, an ordinary account can gain administrative privileges. CISA's catalog entry describes the result as privilege escalation.
Full administrative control of a file-transfer server is serious because these systems often hold exactly the data an attacker wants to steal. The sources do not detail what an attacker could reach on a given server, so defenders should assume the worst until they have checked.
A note on the severity score
One detail in IBM's scoring is worth flagging. The written descriptions say the attacker must be an authenticated or authorized user. The CVSS 3.1 vector IBM published lists Privileges Required: None, along with network attack vector, low attack complexity and no user interaction. That combination is how the score reaches 9.8.
The sources don't explain the mismatch. One possible reading is that any account will do, including a self-registered, guest or external-recipient account where those are enabled. Another is that the vector is simply generous. Defenders shouldn't count on "an attacker needs a login first" as protection. On a Faspex server that partners log into, plenty of accounts exist, and some may belong to people outside your organization.
The timeline
- Nov. 7, 2026: IBM publishes its security bulletin, and the CVE record is published the same day.
- Nov. 9, 2026: CISA adds the flaw to KEV as "IBM Aspera Faspex Incorrect Authorization Vulnerability," with a due date of Nov. 12.
- Nov. 10, 2026: The Hacker News reports that the Faspex bug was one of four flaws CISA added on Monday, alongside FreeSWITCH CVE-2026-116779, OpenSSH CVE-2026-123158 (nicknamed "SSHole") and GPUStack CVE-2026-102895.
Two days from the bulletin to KEV listing is fast, and a three-day remediation window is short. On top of that, CISA set the entry's forensic-triage field to "Yes." That is a strong hint that patching alone may not be enough, and that organizations should look for signs they were compromised before the fix went in.
What we don't know
Nobody has said publicly who is exploiting the flaw, how they are doing it, or how many organizations are affected. The Hacker News reports there are no public reports on how the Faspex flaw and the other newly listed bugs are being exploited or who is behind them. IBM's bulletin does not mention exploitation at all. CISA lists ransomware use as "Unknown," its standard label when it has no confirmed link to a ransomware campaign. That label does not mean ransomware has been ruled out. None of the sources attribute the activity to any group or country.
It also isn't clear whether the exploitation started before IBM's patch, which would make this a true zero-day, or followed quickly after it. The KEV listing confirms exploitation is happening. It does not say when it began.
What It Means for Defenders
Who is affected: Any organization running IBM Aspera Faspex 5.0.0 through 5.0.19. This is urgent for federal civilian agencies, which fall under the KEV due date (Nov. 12, now passed). It also matters for contractors and suppliers who use Faspex to exchange files with government customers. If you are working through CMMC and Faspex carries Controlled Unclassified Information, treat this as a priority finding.
What to patch: Upgrade to Faspex 5.0.19 PL1 on Linux. IBM says to validate that the faspex-core container image is 5.0.19 (build 1ce4b13, Fix Pack 1). If you only upgraded a package and never checked which container image is actually running, you may still be exposed. IBM lists no workarounds or mitigations. If you can't patch, CISA's required action is to apply the vendor mitigations under BOD 26-04 or stop using the product.
What to check: The forensic-triage flag and the bug's impact (a regular user becomes an admin) suggest these steps:
- Audit every Faspex administrator account. Remove any you can't tie to a named, authorized person, and check when existing admin accounts were created or promoted.
- Review Faspex application and access logs for privilege changes, new admin users, configuration changes and unusual package access or downloads. Look as far back as your logs go, not only since Nov. 7.
- Review the non-admin accounts too, especially external, guest or self-registered users. Disable any that are stale.
- Rotate credentials for administrator accounts and for any service accounts or integrations Faspex uses. An attacker with admin access could have viewed or changed them.
- If you find signs of compromise, assume that files transferred through the server may have been exposed, and handle it under your incident response and any contractual or regulatory reporting obligations.
Reduce exposure going forward: If your Faspex server doesn't need to be reachable from the whole internet, restrict access to known partner networks or put it behind a VPN or access proxy. That wouldn't have fixed this bug. It would have limited who could try it.
If Faspex is in your environment, patch it, confirm the container build, and then check who has admin access.