The IBM flaw CVE-2026-123218 in the file transfer software Aspera Faspex is being actively exploited. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its Known Exploited Vulnerabilities (KEV) catalog on 9 November 2026 and gave federal agencies just three days to patch. The bug lets an attacker bypass authorization checks and gain full administrative privileges. IBM rates it CVSS 9.8 and released version 5.0.19 PL1 on 7 November. There is no workaround.
CVE-2026-123218: what IBM describes
According to IBM’s security bulletin, a user of Aspera Faspex 5 can send a specially crafted message that bypasses authorization. The result is privilege escalation up to “full administrative privileges”. IBM classifies the flaw as CWE-863 (Incorrect Authorization): the system does check permissions, just not correctly.
The key facts from the bulletin:
- Affected: IBM Aspera Faspex 5.0.0 through 5.0.19
- Fixed in: Aspera Faspex 5.0.19 PL1 (Linux)
- How to verify: the
faspex-corecontainer image must report version 5.0.19, build 1ce4b13, Fix Pack 1. - CVSS 3.1: 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
- Workarounds and mitigations: none
One detail deserves attention. In its description, IBM speaks of an “authorized user”, meaning an attacker who already has an account. The published CVSS vector, however, sets “Privileges Required: None”, meaning no precondition at all. The bulletin does not say which reading is correct. In practice the difference matters less than it seems: Faspex is designed to give external partners accounts so they can send and collect files. A low-privileged account is therefore often easy to obtain, or already in the wrong hands.
What Aspera Faspex is
Aspera Faspex is IBM’s product for exchanging large files between organisations. It relies on IBM’s own FASP transfer protocol and is used in media production, research, pharmaceuticals and by service providers that regularly move packages in the gigabyte or terabyte range. The software is typically self-hosted in the customer’s own data centre; version 5 runs as a container-based installation on Linux.
Because Faspex exchanges files with outsiders, it is almost always reachable from the internet. And because confidential content passes through it, such as raw footage, contracts and research data, an administrator account is particularly valuable: whoever holds one can read packages, create accounts and change shares. That has made file transfer platforms popular targets for years. Back in 2023, attackers exploited CVE-2022-47986, a flaw in the older Faspex 4.
CISA deadline and what is known about the attacks
CISA listed CVE-2026-123218 in its alert of 9 November together with three other flaws: the GPUStack vulnerability CVE-2026-102895, the FreeSWITCH flaw CVE-2026-116779 and the OpenSSH bug CVE-2026-123158. The deadline for US federal agencies expired on 12 November. The KEV catalog also states that forensic triage is required under directive BOD 26-04. Agencies must therefore not only patch but also determine whether their system was compromised beforehand. CISA lists the flaw’s use in ransomware campaigns as “Unknown”.
Little is known about the attacks themselves. IBM’s bulletin does not mention exploitation, and neither CISA nor security firms have so far published details, attackers or indicators of compromise (IoCs). Canada’s Cyber Centre, in its advisory AV26-1135, also only points to the KEV entry. What we know: according to CISA, there is evidence of attacks. What we don’t know: how many systems are affected and what the attackers did once inside.
The flaw is part of a series we have been following over the past few days: the GPUStack flaw CVE-2026-102895 and the FreeSWITCH flaw CVE-2026-116779 were added in the same KEV update. We covered the OpenSSH issue under the name SSHole.
Why authorization checks fail so often
CWE-863 bugs rarely come from missing checks; they come from incomplete ones. An application may verify that a user is an administrator when a page is opened, but not for every individual action that triggers the same function through a different interface. Or it trusts a field in a message that the user can set themselves. IBM gives no technical detail on which message triggers the problem in Faspex. That is common for actively exploited flaws, so attackers do not get a how-to on top. For defenders, however, it means that targeted detection rules are hard to write right now. That makes the update, and a close look at accounts and permissions that have changed unexpectedly, all the more important.
Who needs to act now
Every organisation that runs Aspera Faspex 5 itself is affected. Users who only receive packages through a partner’s Faspex instance do not need to install anything, but they should expect to hear from that partner if its system has been compromised. The bulletin does not list older Faspex 4 installations as affected. Operators should check for themselves whether those are still supported, because IBM only lists versions within support in its bulletins.
Recommendations for administrators
- Update immediately: move to Aspera Faspex 5.0.19 PL1, then check that the
faspex-corecontainer image really reports build 1ce4b13 with Fix Pack 1. Otherwise a failed update only surfaces at the next incident. - Review accounts: compare the list of administrators and privileged accounts with the expected state. Unknown or recently elevated accounts are a warning sign.
- Check the logs: look for unusual logins, permission changes, new shares and conspicuous downloads since the start of November. This is general advice, not a specific IoC list from IBM.
- Limit exposure: where possible, make the administration interface reachable only from internal networks or via VPN, and restrict partner accounts to what they need.
- Assume compromise: anyone who ran a vulnerable version openly on the internet should follow what CISA requires of agencies: patch first, then investigate forensically. Rotate credentials and API keys stored on the system.
Conclusion
CVE-2026-123218 is a classic authorization flaw, but in a sensitive place: file transfer platforms sit on the internet, have many external users and handle confidential data. With CVSS 9.8, confirmed exploitation and no workaround, there is little to weigh up. Faspex 5 operators should update to 5.0.19 PL1, verify the build and review their accounts and logs, even though details of the attacks are still missing.




