Quick answers
- Is CVE-2026-123218 exploited in the wild?
- Yes. CVE-2026-123218 is known to be exploited in the wild, first recorded on 9 November 2026. Treat it as urgent.
- How severe is CVE-2026-123218?
- Critical severity, with a CVSS score of 9.8, published 7 November 2026.
- Which products and versions are affected?
- IBM Aspera Faspex 5.0.0 through 5.0.19.
- Is there a fix for CVE-2026-123218?
- Yes: fixed in 5.0.19 PL1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123218 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-123218?
- Check whether you run IBM Aspera Faspex at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 5.0.19 PL1
Technical details
A privilege escalation vulnerability exists in Faspex 5.0.0 through 5.0.19 where an authenticated attacker can bypass authorization mechanisms via a specially crafted message (CWE-863: Incorrect Authorization). The vulnerability requires an existing user account but allows unauthenticated elevation to administrative privileges over the network. A fix is available in version 5.0.19 PL1.
Affected products
- IBM Aspera Faspex 5.0.0 through 5.0.19
Timeline
- 2026-11-07: advisory