English edition · cyberattaques.org in FrenchFrançais
VulnerabilityExploited

CISA adds exploited IBM Aspera Faspex authorization flaw to its KEV catalogue

On 9 November 2026 CISA added CVE-2026-123218, an incorrect authorization flaw in IBM Aspera Faspex that lets an authenticated user escalate privileges, to its Known Exploited Vulnerabilities catalogue. Organisations running Faspex are concerned, with US federal agencies facing a 12 November remediation deadline.

What to do now Illustration photo (server room)
CVSS severity9.8Critical
EPSS probability1 %
ExploitationConfirmed (CISA KEV)
PatchNone
Product
IBM Aspera Faspex
Affected versions
—
CVE
CVE-2026-123218

CISA has listed CVE-2026-123218, a vulnerability in IBM Aspera Faspex, in its Known Exploited Vulnerabilities catalogue as of 9 November 2026. Inclusion in the catalogue means the flaw is being exploited in real attacks.

The bug is an incorrect authorization weakness (CWE-863). A user who is already logged in can send a specially crafted message that slips past authorization checks and grants higher privileges than the account should hold. An attacker therefore needs valid credentials, but a low-privilege account may be enough to start from.

The source does not list affected versions or a fixed release. It points to an IBM support page (node 7295921) and tells organisations to follow the vendor's mitigation instructions, or to stop using the product if no mitigation is available. Whether the flaw has been used in ransomware campaigns is listed as unknown.

Under Binding Operational Directive 26-04, US federal agencies have until 12 November 2026 to act, an unusually short window. CISA has also flagged the entry for its forensic triage requirements, meaning agencies are expected to look for evidence of compromise rather than simply patch.

For other organisations, the tight deadline is a reasonable signal of how urgently to treat the issue, especially where a Faspex instance is reachable from the internet.

Action plan

What to do now

  1. Read the referenced IBM advisory (support page 7295921) and apply the fix or mitigations it describes for your Faspex version right away.
  2. If no mitigation applies to your deployment, consider cutting off access to the instance or suspending its use, as CISA advises.
  3. Review Faspex logs and user accounts for unexpected privilege escalations or role changes.
  4. As general good practice, limit internet exposure of Faspex and remove unused or dormant accounts.

Sources