IBM Aspera Faspex: critical CVE-2026-123218 under active attack
IBM Aspera Faspex: critical CVE-2026-123218 under active attack
What it is and who is affectedIBM Aspera Faspex, the enterprise file-transfer platform many organisations use to move large media and data sets betwee...
What it is and who is affected
IBM Aspera Faspex, the enterprise file-transfer platform many organisations use to move large media and data sets between teams and partners, carries a critical authorization flaw tracked as CVE-2026-123218. IBM describes it as an incorrect authorization vulnerability (CWE-863): an authenticated user can craft a specific message that bypasses authorization checks and escalates privileges.

The NVD entry is blunt about the impact. According to NIST, IBM Aspera Faspex 5.0.0 through 5.0.19 could allow an authorized user to craft a specific message, bypass user authorization and gain full administrative privileges. The affected range is listed as from 5.0.0 inclusive up to, but not including, 5.0.19.1.
The severity is CVSS 3.1 score of 9.8, rated CRITICAL, with a vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. In plain terms: reachable over the network, low complexity, and with a high impact on confidentiality, integrity and availability. The record was published in the NVD on 7 November 2026.
This matters well beyond large enterprises. Any Spanish SME, e-commerce business or media company running Faspex on its own infrastructure, or through a small IT team that inherited the platform years ago, should treat it as a priority item. The same applies to agencies and integrators in Barcelona, Lleida, Tarragona or Girona who host Faspex for their clients.
Why it is urgent: already exploited in real attacks
This is not a theoretical flaw waiting for a proof of concept. CISA added CVE-2026-123218 to its Known Exploited Vulnerabilities (KEV) catalogue on 9 November 2026, which means there is confirmed exploitation in real-world attacks.
CISA gave US federal agencies until 12 November 2026 to remediate, and its required action is to apply mitigations in line with the vendor's instructions, following its BOD 26-04 guidance on prioritising security updates by risk and its forensics triage requirements. CISA also notes that where mitigations are unavailable for cloud services, the product should be discontinued, and that each organisation must assess the internet exposure of its own assets.
Two details deserve emphasis. First, the material does not record this vulnerability as used in ransomware campaigns, so it should not be described as a ransomware vector. Second, the short window between publication and KEV listing tells you how quickly attackers move once a privilege-escalation path in a file-transfer product becomes public. Faspex instances typically hold sensitive documents and sit on networks with trusted connections to partners, which makes an admin-level compromise especially damaging under GDPR obligations.
What to do today
- Inventory first. Check whether IBM Aspera Faspex is running anywhere in your estate, including subsidiaries, marketing departments and any server a managed provider operates on your behalf. Record the exact version.
- Compare against the affected range. If you are on any release from 5.0.0 up to but not including 5.0.19.1, you are in scope. Confirm the precise build rather than assuming.
- Apply the vendor's fix or mitigation. Follow IBM's advisory (support page node 7295921) for the corrected release and any interim mitigation it prescribes. Do not guess a version number: use exactly what the vendor notice states.
- Look for signs of intrusion. Because the flaw allows an authenticated user to reach administrative privileges, review accounts, role changes, unusual message activity and administrative actions in the period since exposure. CISA's forensics triage guidance is a sensible reference for structuring that review.
- Reduce what is exposed to the internet. Restrict access to known partner addresses, place the service behind a reverse proxy or VPN where feasible, enforce strong authentication and least privilege, and log everything.
If you cannot patch immediately, treat the exposure assessment as the priority: an internet-facing Faspex instance on an affected version is the worst combination.
How a cybersecurity team like ALMC's can help
Most SMEs and online shops do not have the internal capacity to chase vendor advisories, verify versions across a mixed estate and then audit for intrusions in the same week. That is the gap ALMC fills: we detect and close vulnerabilities before they are exploited, through security audits and pentesting, server hardening, monitoring and incident response.
For organisations running WordPress, PrestaShop or Joomla alongside business platforms such as Faspex, we also handle ongoing maintenance and patching of those CMSs and the repair of sites that have already been compromised. The practical value is a clear picture of what is exposed, a prioritised remediation list based on real risk, and someone who responds when an alert fires. If your team is small, that continuity is often the difference between a patched system and an incident report.
Related
- Ivanti Connect Secure: CVE-2026-104935 Under Active Attack
- CVE-2026-96951: Windows Shell Command Injection Under Attack
- Click to Chat for WhatsApp: CVE-2026-92097 in WordPress
- Abuse Shield
Is your business exposed to flaws like this?
ALMC checks which versions you are running, applies the patches and hardens your servers and website. Contact our team for a security review.
