IBM Aspera Faspex
CISA added this flaw to KEV on 2026-11-09 with an unusually short three-day remediation deadline, and Faspex servers not yet on 5.0.19 PL1 are exposed to attackers who can take administrative control of the transfer system and the data it holds.
IBM Aspera Faspex 5.0.0 through 5.0.19 incorrectly enforces authorization, letting a user craft a specific message to bypass authorization checks and gain full administrative privileges on the file-transfer server. IBM rates it CVSS 9.8 and offers no workaround other than upgrading.
Affected: IBM Aspera Faspex 5.0.0 - 5.0.19
Check the running Faspex version: anything in the 5.0.0–5.0.19 range without PL1 is vulnerable; after upgrading, validate that the faspex-core container image is 5.0.19 (1ce4b13, Fix Pack: 1). Review Faspex application and access logs for unexpected privilege changes, new or modified administrator accounts, and administrative actions performed by ordinary user accounts.
Upgrade to IBM Aspera Faspex 5.0.19 PL1 (Linux) following IBM's fix instructions; IBM lists no workarounds or mitigations, so if the upgrade must wait, restrict network access to the Faspex server to trusted sources in the interim.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
