IBM Aspera Faspex Authorization Bypass
Affects IBM Aspera Faspex 5.0.0 through 5.0.19. Fixed in 5.0.19 PL1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.0.19 PL1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.0.19 PL1.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.40% · 34th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 27/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
IBM Aspera Faspex is affected by an authorization bypass that an attacker can reach remotely over the network, without logging in or any user action. Successful exploitation lets the attacker gain full administrative privileges.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 9.8
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.0.19 PL1.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- IBM Aspera Faspex
From 5.0.0 · through 5.0.19
Evidence 1
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123218
Is CVE-2026-123218 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authorized user can bypass user authorization and gain full administrative privileges.Source: ibm.com
Which versions are affected by CVE-2026-123218?
Aspera Faspex: from 5.0.0 through 5.0.19.Source: cve.now feed data
Am I affected, and how do I check?
IBM Aspera Faspex versions 5.0.0 through 5.0.19 are listed as affected. The installed Faspex version is the setting to check against that range.Source: ibm.com
How do I fix CVE-2026-123218?
Upgrade to IBM Aspera Faspex 5.0.19 PL1, the fixed version listed for Linux.Source: ibm.com