CVE-2026-123218

IBM Aspera Faspex privilege escalation, confirmed exploited in the wild.

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.

Check your domain free How we watch for this

0.5%chance of exploitation in the next 30 days (EPSS), 45th percentile

9 Novadded to CISA's Known Exploited Vulnerabilities list, 2026

12 Novfederal remediation deadline, already passed

Passedpast the deadline: patch now

CISA's name for it	IBM Aspera Faspex Incorrect Authorization Vulnerability
Vendor and product	IBM · Aspera Faspex
Type	privilege escalation · CWE-863
Exploited	Confirmed by CISA listed 9 November 2026
Likelihood	scored lower by EPSS, but already confirmed exploited, which outranks any prediction
Deadline	12 November 2026 · already passed
Used in ransomware	Not reported
Advisories	www.ibm.com ↗ · www.cisa.gov ↗ · www.cisa.gov ↗ · nvd.nist.gov ↗

What to do

Three steps, in this order

Step 1

Install the update on every affected system, servers and workstations alike.

Step 2

Escalation bugs are chained after a first foothold: check for other exposures an attacker could start from.

Step 3

Review who holds administrative rights, and alert on new ones.

CISA's 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.

CISA's 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.

Is it on your estate?

Know before someone else finds it

Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.

Start free with one domain Run the free domain check

Questions

CVE-2026-123218 in short

Is CVE-2026-123218 being exploited?

Yes. CISA added CVE-2026-123218 to its Known Exploited Vulnerabilities catalogue on 9 November 2026, which it does only on evidence of exploitation in the wild.

What is the CISA deadline for CVE-2026-123218?

US federal agencies must remediate it by 12 November 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.

How likely is CVE-2026-123218 to be exploited in the next 30 days?

FIRST's Exploit Prediction Scoring System gives it 0.5%, the 45th percentile of every CVE it scores.

How do I fix CVE-2026-123218?

Install the update on every affected system, servers and workstations alike. Escalation bugs are chained after a first foothold: check for other exposures an attacker could start from. Review who holds administrative rights, and alert on new ones.

Same vendor

Other IBM vulnerabilities being exploited

CVE	Product	Type	Listed
CVE-2026-9198	Langflow	remote code execution	4 August 2026

Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.