IBM Aspera Faspex Incorrect Authorization Vulnerability
- What it is
- 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.
- Who's affected
- Anyone using IBM Aspera Faspex.
- Under attack?
- Yes. CISA added this to its catalog of actively exploited vulnerabilities on Nov 9, 2026.
- What to do
- Install the vendor's security update. If there isn't one yet, apply the vendor's workaround, or stop using the product until it's fixed. CISA lists this as actively exploited, so treat it as urgent.
- Fixed in
- See the vendor's advisory
- Zero-day?
- Yes. CISA listed it as exploited 2 days after it went public, so attacks began before most people could patch.
- CISA deadline
- Federal agencies must fix this by Nov 12, 2026. Everyone else should treat that as a ceiling, not a target.
- CISA's instruction
- 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.
Attack timeline
- Nov 7, 2026Went publicThe flaw was published with its CVE number.
- Nov 9, 2026+2 daysCISA listed it as exploitedAdded to CISA's Known Exploited Vulnerabilities catalog.
- Nov 12, 2026+3 daysFederal fix deadlineU.S. agencies must have it fixed by this date.
IBM scorecard: every exploited IBM flaw →
Client notice ready to send
Fill in the bracketed parts, then paste into an email to your clients or team.