Skip to content
skopnix

CVE-2026-123218 · Published 7 Nov 2026

IBM Aspera Faspex

On CISA's KEV list 2 days after disclosure; 1 public exploit.

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.

CISA required action (federal due date 12 Nov 2026): 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.

Signals

KEV, exploited in the wild
yes, added 9 Nov 2026, due 12 Nov 2026
EPSS, 30-day forecast
0.5%, 46th percentile (as of 18 Nov 2026)
CVSS, NVD
not stated
Internet exposure
not stated

KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.

Timeline 7 Nov 2026 to today

2 days from disclosure to the KEV listing
Disclosed 7 Nov 2026KEV 9 Nov 2026First PoC 10 Nov 2026today
  1. Disclosed
  2. KEV+2 d
  3. First PoC+1 d

2 days from disclosure to the KEV listing

Indicators none tied yet

No threat feed has tied an indicator to this CVE yet. Checked every six hours.

On the wire 1 dispatch

  1. CISA adds CVE-2026-123218 (IBM Aspera Faspex) to the Known Exploited Vulnerabilities catalog · KEV

Public exploit code 1 known · links only

GitHub PoCs 1Metasploit 0Exploit-DB 0

GitHub PoCs, by trust then stars1

  1. foxcornlab/faspex-scannerTrust ok 1000 stars

    Detection-only triage for IBM Aspera Faspex CVE-2026-123218 (CVSS 9.8, CISA KEV): grades Faspex 5 installs against the 5.0.19 PL1 fix, catches the bare-5.0.19 trap.

    created 10 Nov 2026

Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.

References

Watch this one?

KEV additions reach Telegram and the KEV-only RSS as they land.

Telegram ↗KEV RSSAPIStack check