ZeroDayAlert

CVE-2026-123218: IBM Aspera Faspex Incorrect Authorization Vulnerability

IBM Aspera Faspex contains an incorrect authorization vulnerability that could allow an authenticated user to craft a specific message to bypass authorization, causing privilege escalations.

IBM Aspera Faspex Added to KEV 2026-11-09 Federal due 2026-11-12 Known ransomware use

Required action — quoted from CISA

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Where this comes from. The identifier, product, dates and required action above are copied verbatim from the CISA Known Exploited Vulnerabilities catalog. The action plan below is written by an AI agent from that record and published automatically. AssurePort has not independently tested this vulnerability and makes no claim about whether any specific system is affected.

Who is affected

IBM Aspera Faspex is affected by an incorrect authorisation vulnerability that permits authenticated users to escalate their privileges by crafting specific messages that bypass access controls. The vulnerability applies to Faspex deployments where unauthorised privilege escalation poses a risk; the record does not specify which versions or deployment topologies are in scope.

How to check whether this touches you

  • Inventory your environment for any running instance of IBM Aspera Faspex, including non-production and backup instances.
  • Determine whether Faspex is reachable from the internet or from untrusted network segments where unauthenticated or low-privileged users could obtain access.
  • Establish the running version number from the administrative interface or package metadata; consult IBM's advisory to map your version against the affected range and any available patches.
  • Review access logs to identify the population of authenticated users with current or recent sessions.

What to do

  1. Obtain IBM's remediation guidance immediately and assess whether a patch is available for your version. If a patch exists, schedule its application within the federal remediation window.
  2. If no patch is available, implement network segmentation to restrict access to Faspex to authorised users and networks only; disable or isolate internet-facing endpoints if feasible.
  3. Review and tighten role-based access controls within Faspex to limit the blast radius of any unauthorised privilege escalation; document the current privilege model.
  4. Enable and retain detailed audit logging of authentication, authorisation decisions, and administrative actions within Faspex and any proxy or load-balancer in front of it.
  5. If you cannot patch or mitigate within the federal remediation due date, escalate to your security leadership and evaluate discontinuation of the product in accordance with CISA BOD 26-04 guidance.

If you find you were exposed

Exploitation of an authorisation bypass typically precedes public disclosure by weeks or months. Search your audit logs for authenticated sessions that performed administrative or sensitive operations outside their known role; pay particular attention to session-start times and the timeline of the advisory. Retention of logs is your primary constraint; if you cannot access logs older than 90 days, document the gap and flag it as a detection risk for future incidents.

Get these the morning they land.

One email, only when a vulnerability is newly confirmed as exploited — the CISA record plus our action plan. No more than one a day, and nothing on quiet days.

Knowing it exists is not the same as knowing you are exposed.

This page can tell you that CVE-2026-123218 is being exploited. It cannot tell you whether Aspera Faspex is running somewhere of yours that is reachable. That question is what a scan answers.

Check your own surface →