Exploited CVEs / IBM / CVE-2026-123218

CVE-2026-123218

IBM Aspera Faspex Incorrect Authorization Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-11-12 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Senserva AI read on CVE-2026-123218CISA required actionOfficial fix for CVE-2026-123218Admin questions#8 hottest CVE right now

Risk summary

In the top 10 of the Senserva CVE Ranking (as of 2026-11-14)
CriticalCISA KEV
9.8
CVSS v3 base
<1%
EPSS exploit probability
Critical
Severity
2026-11-09
Added to KEV
2026-11-12 (past due)
CISA due date

Actively exploited IBM Aspera Faspex vulnerability, Critical severity, CVSS v3 9.8. Added to the CISA KEV catalog 2026-11-09.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Federal remediation deadline 2026-11-12; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated November 9, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Senserva AI Opinion for CVE-2026-123218

CVE-2026-123218 is an incorrect authorization flaw in IBM Aspera Faspex where an authenticated user can send a specially crafted message to bypass authorization checks and escalate privileges. The Severity is Critical (CVSS 9.8), and CISA added it to the KEV catalog on 2026-11-09, confirming real-world exploitation even though the EPSS probability is only 1% and no ransomware use is known. The EPSS figure understates the risk here: any Faspex deployment where users can log in, including low-trust external accounts, should be treated as exposed.

Do this: Apply IBM's fix for Aspera Faspex today, and until it is deployed, restrict Faspex access to trusted networks and review recent accounts and privilege changes for signs of escalation.

AI-generated from public data, 2026-11-11. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-123218

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Full tracking and change history for CVE-2026-123218

Published
2026-11-09
Last revised
2026-11-09
Changes tracked
2

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when

CISA added CVE-2026-123218 to its KEV catalog on 2026-11-09, which confirms exploitation in the wild and is the strongest signal here. EPSS then scored it only 0.7% on 2026-11-10 and slipped to 0.5% by 2026-11-13. The falling model estimate does not outweigh the KEV listing, so treat this as a patch-soon item.

0%25%50%75%100%CISA KEVCISA KEV on 2026-11-092026-11-10: EPSS 0.7%2026-11-10: EPSS 0.7%2026-11-13: EPSS 0.5%2026-11-13: EPSS 0.5%EPSS 0.5%2026-11-092026-11-13

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

  • 2026-11-09 added to the CISA KEV catalog by CISA
  • 2026-11-10 EPSS first scored at 0.7%
  • 2026-11-13 EPSS 0.7% to 0.5%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

From the Senserva blog

CISA required action

Federal remediation due date: 2026-11-12 (past due).

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.

Official fix for CVE-2026-123218

Check the vendor's security advisory channel for the patched Aspera Faspex versions and workarounds.

Common questions about CVE-2026-123218

Is CVE-2026-123218 actively exploited?

Yes. CVE-2026-123218 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-11-09, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is <1%.

What is the CISA deadline and required action for CVE-2026-123218?

CISA set the federal remediation due date at 2026-11-12, which has passed; treat any unremediated system as overdue. The verbatim required action: 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.

What fixes CVE-2026-123218?

Check the vendor's security advisory for the patched Aspera Faspex versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-123218?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-123218's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed daily (early morning US Central).

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
All information provided as is, without warranty; verify against the vendor advisory before acting. All information and usage is subject to the Senserva EULA. Data notice and terms.