IBM Aspera Faspex Flaw CVE-2026-123218: Update Now
Published November 8, 2026 · Last updated November 8, 2026
The short version: CVE-2026-123218 is a critical-severity security flaw in IBM Aspera Faspex. The National Vulnerability Database (NVD) published it on November 7, 2026, and the score it lists is 9.8 out of 10. NVD records that CISA added CVE-2026-123218 to the Known Exploited Vulnerabilities catalog on November 9, 2026, with an action due date of November 12, 2026. A fix is available, which is why this page focuses on who should update and how.
On November 8, 2026, the stored FraudMeNot record for CVE-2026-123218 had no CISA KEV add date. The November 9 NVD record lists a CISA add date of November 9, 2026 and an action due date of November 12, 2026. The November 9 CISA catalog entry lists known ransomware campaign use as Unknown.
What the official record says about CVE-2026-123218
The record was filed by us.ibm.com. In its own words: "IBM Aspera Faspex 5.0.0 through 5.0.19 could allow an authorized user to craft a specific message to bypass user authorization and gain full administrative privileges."
Why Aspera Faspex admins should care
Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on us.ibm.com rated CVE-2026-123218 9.8 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Aspera Faspex running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Affected Aspera Faspex releases
According to the record, these releases are vulnerable:
- 5.0.0 through 5.0.19
The type of bug behind CVE-2026-123218
NVD classifies it using MITRE's Common Weakness Enumeration:
- CWE-863, Incorrect Authorization. MITRE describes this class of bug as follows: "The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check."
Vendor remediation for CVE-2026-123218
The vendor advisory remediation for operators of Aspera Faspex, quoted for this page, is: "Install IBM Aspera Faspex 5.0.19 PL1 on Linux, then confirm faspex-core reports 5.0.19 (1ce4b13, Fix Pack: 1), per IBM security bulletin 7295921. IBM lists no workaround. Caveat on the score: IBM's 9.8 CVSS vector says no privileges are required (PR:N), but IBM's own description says an authorized user must craft the message, so the attacker needs a Faspex account. Treat any account holder, including external users you invited, as a potential path to full administrator access until patched. While you schedule the fix pack, review which Faspex accounts exist, remove stale or unneeded users, check recent changes to administrator roles and system settings, and keep the Faspex web interface off the open internet where your workflow allows. Faspex often exchanges large files with partners, so prioritize servers reachable by outside organizations, and tell partner contacts to expect no unusual password-reset or package requests during maintenance."
What to do about it
- Update now: Install IBM Aspera Faspex 5.0.19 PL1 on Linux, then confirm faspex-core reports 5.0.19 (1ce4b13, Fix Pack: 1), per IBM security bulletin 7295921. IBM lists no workaround. Caveat on the score: IBM's 9.8 CVSS vector says no privileges are required (PR:N), but IBM's own description says an authorized user must craft the message, so the attacker needs a Faspex account. Treat any account holder, including external users you invited, as a potential path to full administrator access until patched. While you schedule the fix pack, review which Faspex accounts exist, remove stale or unneeded users, check recent changes to administrator roles and system settings, and keep the Faspex web interface off the open internet where your workflow allows. Faspex often exchanges large files with partners, so prioritize servers reachable by outside organizations, and tell partner contacts to expect no unusual password-reset or package requests during maintenance.
- Who should act: IT teams, managed service providers, and developers who run or ship Aspera Faspex. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
- Read the official advisory from IBM (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
- After patching, confirm the new version is actually running and review logs from November 7, 2026 onward for anything unusual.
- Home users: you do not need to buy or download anything because of CVE-2026-123218. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.
CVE-2026-123218 record details from CISA and NVD
- CISA KEV entry in NVD: added November 9, 2026, action due November 12, 2026.
- Attack complexity for CVE-2026-123218: low
- CVE-2026-123218 CVSS scope: unchanged
- NVD sub-scores for CVE-2026-123218: exploitability 3.9, impact 5.9.
- Who mapped the weakness type: the address listed on us.ibm.com (Primary)
- References in the NVD record: 1.
Dates to know
- November 7, 2026: NVD publishes CVE-2026-123218.
- November 9, 2026: NVD records a CISA KEV add date for CVE-2026-123218.
- November 9, 2026: most recent NVD update (record status: Undergoing Analysis).
Official references
Links listed in the NVD record (labels in brackets come from NVD):
Sources
General education only, not security advice. Facts checked against the sources above on the date shown.