All articles

NewsNovember 7, 20264 min read

IBM Aspera Faspex, CVE-2026-123218: admin access exploited

IBM Aspera Faspex 5.0.0 through 5.0.19: a crafted message bypasses authorization and grants full admin privileges. Exploited, listed in CISA KEV.

Chains and a padlock labelled “Data Locker” on a background of green binary code

On 9 November 2026 CISA, the US cybersecurity agency, added CVE-2026-123218 to its Known Exploited Vulnerabilities (KEV) catalog. It is an incorrect authorization vulnerability in IBM Aspera Faspex, IBM’s file exchange platform. Inclusion in the catalog means CISA has evidence of active exploitation. According to the National Vulnerability Database (NVD) entry, the flaw allows an attacker to gain full administrative privileges on the application.

The information in this article comes from the KEV catalog entry and the linked NVD record, which report the same data. The sources do not say who exploited the vulnerability, against which organizations or with what goal.

How the vulnerability works

The description published on NVD is short: in IBM Aspera Faspex 5.0.0 through 5.0.19, an authorized user can craft a specific message that bypasses authorization checks and grants them full administrative privileges.

The weakness listed is CWE-863 (Incorrect Authorization): the application verifies who the user is but does not correctly check what they are allowed to do. The sources do not describe the message format, the component involved or the attack chain used in the observed exploitation.

One point is worth noting. The description refers to an authorized user, while the CVSS vector given for the same vulnerability states that no privileges are required (PR:N). The sources do not explain the difference: as a precaution, it is best to assume the more severe vector, meaning the attack may not require an account.

Technical details

  • CVE: CVE-2026-123218, published on NVD on 7 November 2026, analysed and updated on 10 November.
  • Affected versions: according to the description, IBM Aspera Faspex 5.0.0 through 5.0.19; the affected product configuration in NVD covers versions from 5.0.0 up to, but excluding, 5.0.19.1.
  • Weakness: CWE-863 (Incorrect Authorization).
  • CVSS 3.1: 9.8, critical, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, assigned by IBM’s PSIRT: network attack, low complexity, no privileges and no user interaction required, high impact on confidentiality, integrity and availability.
  • KEV catalog: added on 9 November 2026; the deadline for US federal agencies to act is 12 November 2026, three days later. Use in ransomware campaigns is listed as “unknown”.
  • Vendor reference: the IBM security bulletin (support page 7295921), listed by NVD as the vendor advisory.
  • MITRE ATT&CK: for an instance reachable over the network, the matching technique is T1190 (Exploit Public-Facing Application).

The sources do not report indicators of compromise.

Impact for European and Italian companies

A file exchange platform such as Aspera Faspex manages user accounts and the files companies exchange with customers, suppliers and partners. Access with administrator privileges gives control over the application, and the CVSS score indicates a high impact on confidentiality, integrity and availability.

The 9.8 score and the KEV listing show that the flaw is severe and already exploited; the three-day deadline CISA set for federal agencies shows how urgent the agency considers it.

For entities in scope of NIS2, managing known vulnerabilities and patching promptly are part of the required security measures; the KEV catalog, which is binding only on US federal agencies, is still a useful guide for setting priorities. Where the platform is used to exchange health or personal data, a compromise may also trigger notification obligations under the GDPR.

What to do now

  1. Check the version of IBM Aspera Faspex you run: according to the sources, versions 5.0.0 through 5.0.19 are affected.
  2. Apply the fixes or mitigations described in the IBM security bulletin. The NVD configuration excludes 5.0.19.1 and later, but the sources do not explicitly name the fixed version: check the vendor bulletin. CISA asks organizations to apply mitigations per the vendor’s instructions and, if none are available, to stop using the product.
  3. Reduce exposure: CISA calls for assessing the internet exposure of every installation. Check whether the Faspex interface is reachable from networks that do not need it and restrict access.
  4. Review accounts: look for administrators you do not recognise, recent role or permission changes and configuration changes, especially on instances that stayed exposed with a vulnerable version.
  5. Preserve logs before working on suspicious instances: for federal agencies CISA points to its forensic triage requirements, and for companies too the logs are needed to understand what happened.

How ARXDOME helps

ARX Expose shows what can be seen of your company from the outside, with open ports, recognised products and known vulnerabilities on public services: a file exchange application exposed to the internet comes to light. ARX Horizon weighs vulnerabilities against the catalog of exploited ones, updated daily, so a flaw like CVE-2026-123218 rises to the top of the priority list. ARX Sentry collects logs and events from monitored machines, useful for hunting suspicious activity on the servers that host the platform.

Last updated:

Any questions?

Let’s talk about your company’s needs, with no obligation.

Contact us

Related articles