Skip to content
eastbaycyber

CVE-2026-123218: IBM Aspera Faspex Authorization Bypass

CVSS · Critical
9.8
In CISA KEV
Yes
Published
Nov 13
Patch SLA & TriageVector: Network
Immediate (BOD 22-01 due 2026-11-12)

Active exploitation confirmed in CISA KEV.

Exposure:
Control:
CVSS v3.1 Blast RadiusCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Decode Vector & Sub-Scores →
CVE explainers 10 min read
Security Research Desk Source-checked
Auto-checked against the official CVE record · Human-reviewed after publishing · Updated 2026-11-13
⚠
CISA Known Exploited Vulnerability

Active exploitation confirmed in the wild. CISA added this to the KEV catalog on 2026-11-09. Federal agencies must patch by 2026-11-12.

Everything CISA added on 2026-11-09

▲ Escalation ViewOne CVE, briefed at three altitudes — skim the Brief, weigh the Impact, or work the Runbook. The way a SOC actually reads it.
CISOBrief · 30-second brief

TL;DR - CVE-2026-123218 is a CVSS 9.8 authorization-bypass vulnerability in IBM Aspera Faspex 5.0.0 through 5.0.19. - CISA confirms exploitation in the wild; upgrade to Faspex 5.0.19 PL1. - Prioritize internet-facing systems, restrict exposure, and investigate administrative activity.

CVE-2026-123218 is a critical IBM Aspera Faspex vulnerability affecting versions 5.0.0 through 5.0.19. CISA has added the flaw to its Known Exploited Vulnerabilities catalog, so organizations should treat unpatched deployments as an urgent security risk.

Vulnerability at a Glance

Field Details
CVE ID CVE-2026-123218
Product IBM Aspera Faspex
Vulnerability type CWE-863, Incorrect Authorization
CVSS v3.1 score 9.8 Critical
CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector Network
Authentication or privileges required None under the published CVSS assessment
Affected versions 5.0.0 through 5.0.19
Fixed version 5.0.19 PL1
Patch available Yes
Public PoC No verified public PoC identified in the referenced primary-source material
Active exploitation Confirmed by CISA KEV listing
Published 2026-11-07
Last NVD modification 2026-11-10

CVE-2026-123218 affects IBM Aspera Faspex 5, a file-transfer and collaboration platform. IBM describes the issue as allowing an authorized user to craft a specific message that bypasses authorization and gains full administrative privileges. The published CVSS vector assigns no required privileges, so defenders should not rely on authentication as a sufficient control.

CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on 2026-11-09, with a federal remediation deadline of 2026-11-12. That deadline has passed as of this article’s publication date, making any unpatched deployment a high-priority remediation target.

Analyst’s Take: Patch internet-facing Faspex systems first, then verify internal, test, disaster-recovery, and containerized deployments. The authorized-user wording in IBM’s description conflicts with the CVSS PR:N assessment, so access controls should be treated as exposure reduction rather than proof that an instance is safe.

What Is This Vulnerability?

The flaw is an incorrect authorization vulnerability, classified as CWE-863. Faspex fails to correctly enforce whether a requesting party is permitted to perform an administrative or privileged action. IBM’s description identifies a specially crafted message as the trigger. Successful exploitation can result in full administrative privileges.

The impact is substantial because an administrative account or equivalent control over Faspex can affect confidentiality, integrity, and availability. An attacker could potentially access sensitive transferred files, alter application settings, create or modify accounts, change workflows, or disrupt file-transfer operations. The available vendor material does not publish a complete exploit chain or message format, so defenders should avoid assuming that only a narrow administrative function is affected.

The CVSS vector is worth interpreting carefully. IBM’s description refers to an “authorized user,” while the CVSS vector specifies PR:N, meaning no privileges are required under the scoring model. Treat this discrepancy conservatively: the service may be remotely exploitable without depending on a trusted-user boundary, especially when it is internet-facing.

Technical Notes

The published technical description does not provide a reproducible payload, endpoint, or message schema. The known mechanism is a crafted message that causes Faspex authorization checks to be bypassed. Organizations should avoid inferring a safe allowlist from the limited public description.

A successful attack may leave evidence in message-processing logs followed by administrative activity. Log names and formats vary by deployment, and IBM’s referenced material does not establish a universal event identifier. Detection should correlate message submission with unexpected privileged actions rather than depend on one exact string.

AnalystImpact · assess the risk

Who Is Affected?

The affected product is IBM Aspera Faspex 5. The IBM advisory identifies versions 5.0.0 through 5.0.19 as vulnerable. Deployments should be considered affected unless their installed release is demonstrably outside that range or IBM’s fixed release has been applied and validated.

The risk applies to externally hosted, self-managed, and containerized deployments. Internet exposure increases the likelihood of opportunistic exploitation, but an internally reachable Faspex instance can also be targeted through compromised accounts, adjacent systems, VPN access, or other footholds. Asset inventories should include production, disaster-recovery, test, and externally managed instances.

Faspex version Status
5.0.0–5.0.18 Affected
5.0.19 Affected
5.0.19 PL1 Fixed release identified by IBM
Other versions Status not established by the supplied advisory details; verify directly with IBM

Container operators should verify both the Faspex application version and the deployed image or fix-pack state. A host-level inventory that only records an operating-system package may miss the vulnerable application container.

CVSS Score Breakdown

CVE-2026-123218 has a CVSS v3.1 base score of 9.8, rated Critical. Its vector is:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Metric Value Operational meaning
Attack Vector Network The vulnerable functionality can be reached over a network
Attack Complexity Low Exploitation does not depend on unusual conditions according to the score
Privileges Required None The CVSS assessment does not require prior privileges
User Interaction None No separate victim action is required
Scope Unchanged Impact remains within the vulnerable security authority
Confidentiality High Sensitive data may be exposed
Integrity High Data or configuration may be modified
Availability High Service operation may be disrupted

The score indicates a remotely reachable, low-complexity issue with maximum impact across all three CIA dimensions. It does not, by itself, prove that every deployment is exploitable from the public internet. Network controls, authentication architecture, segmentation, and product configuration still affect practical exposure.

The CISA KEV listing changes the risk calculation. Treat the vulnerability as an active exploitation problem rather than defer action based on environmental assumptions. A system that is not directly internet-facing still requires prompt remediation if it is reachable from user, partner, transfer, or management networks.

Exploitation Status

Exploitation in the wild is confirmed. CISA lists CVE-2026-123218 in the Known Exploited Vulnerabilities catalog. The entry identifies the issue as the IBM Aspera Faspex Incorrect Authorization Vulnerability and requires remediation under applicable CISA guidance.

CISA reports known ransomware campaign use as unknown. “Unknown” does not mean that ransomware use has been ruled out; it means the available CISA entry does not confirm such use. Defenders should separately investigate credential abuse, data access, privilege changes, persistence, and lateral movement.

No verified public proof-of-concept repository was identified in the referenced primary-source material. IBM’s public description also does not provide a detailed exploit procedure. The absence of a public PoC is not a reason to reduce urgency because KEV inclusion independently confirms real-world exploitation.

Technical Notes

For incident response, preserve application, reverse-proxy, load-balancer, identity-provider, and container-orchestration logs before rotating or rebuilding systems. Record timestamps in UTC where possible and correlate message submissions with administrative events.

Investigators should look for patterns such as:

message submitted -> authorization failure or unexpected role decision
                     -> administrative action from same session/IP
                     -> new account, role change, configuration update,
                        package/share modification, or bulk file access

This is a behavioral detection pattern, not a vendor-confirmed literal log string. Do not treat the absence of a matching string as evidence that exploitation did not occur. Compare administrative actions against known maintenance windows, administrator source addresses, and approved change records.

ResponderRunbook · act now

How to Detect It

Start with reliable version discovery. Check the Faspex administration interface, IBM deployment records, container manifests, and fix-pack documentation. For containerized environments, inspect the running image and deployment metadata rather than relying only on the host package inventory.

A practical inventory query should identify every deployment in the affected range:

product = "IBM Aspera Faspex"
version >= "5.0.0"
version <= "5.0.19"
status != "5.0.19 PL1"

The exact implementation depends on the organization’s asset-management system. Version comparison must be numeric and product-aware; string sorting can incorrectly order values such as 5.0.9 and 5.0.19.

Detection should also focus on unexpected privilege escalation and administrative changes. Review Faspex audit records and surrounding infrastructure logs for newly created accounts, role assignments, changes to transfer policies, modified shares, altered authentication settings, and administrative access from unfamiliar addresses. Pay particular attention to activity shortly after message submission or message-processing errors.

Technical Notes

A SIEM correlation rule can use a sequence similar to the following pseudocode:

sequence by session_id or source_ip within 15 minutes:
  faspex.message_submission
  followed_by faspex.authorization_error OR faspex.message_processing_event
  followed_by faspex.admin_action
where admin_action not in approved_change_window
  or actor not in approved_admin_group
  or source_ip not in known_admin_networks

If Faspex does not expose a stable event taxonomy, normalize available web, application, and audit logs into fields such as timestamp, source_ip, user, session_id, request_path, action, role, and result. Alert on suspicious combinations rather than a single path or user-agent value, because the supplied advisory does not define a reliable network signature.

For potentially compromised systems, preserve evidence and follow organizational incident-response procedures. CISA recommends forensic triage in connection with KEV remediation. Do not destroy the original container, volume, or logs before collecting evidence unless containment requires it.

Mitigation and Patching

Upgrade IBM Aspera Faspex from any affected release, 5.0.0 through 5.0.19, to 5.0.19 PL1, following IBM’s installation and validation instructions. The supplied IBM material identifies 5.0.19 PL1 as the fixed release. Confirm the installed version after the change and retain upgrade records for audit and incident-response purposes.

Until patching is complete, restrict access to vulnerable instances. Prefer removing direct internet exposure, limiting access through a tightly controlled administrative network, applying allowlists at the reverse proxy or firewall, and separating Faspex from untrusted user networks. These controls reduce exposure but do not fix the authorization defect.

No permanent workaround was identified in the retrieved vendor material for systems that cannot be upgraded. Do not assume that disabling an individual account, requiring stronger authentication, or placing the service behind a proxy eliminates the vulnerability. Those measures may reduce some attack paths, but the authorization flaw remains present.

For broader vulnerability-management context, review our guidance on CVE patching and vulnerability response and compare incident reporting responsibilities with controller versus processor obligations.

Technical Notes

A generic deployment workflow should be adapted to IBM’s supported procedure and your environment:

# Record the currently deployed Faspex release and image
kubectl -n <namespace> get deploy,pods -o wide
kubectl -n <namespace> describe deployment <faspex-deployment>

# After applying IBM's Faspex 5.0.19 PL1 deployment instructions,
# confirm the running image and rollout status
kubectl -n <namespace> rollout status deployment/<faspex-deployment>
kubectl -n <namespace> get pods -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.spec.containers[*].image}{"\n"}{end}'

Do not substitute an arbitrary image tag or manually alter the faspex-core container without IBM’s documented instructions. Search results associated with the IBM advisory reference validation of the faspex-core image against build 1ce4b13 for Fix Pack 1, but operators should use IBM’s authoritative installation guidance to determine the correct image and validation process for their deployment.

For non-containerized systems, use IBM’s approved Fix Pack 1 installation procedure rather than a generic package-manager command. After upgrading, validate the application version, restart or roll out all relevant components as directed by IBM, and confirm that reverse proxies and health checks point only to fixed instances.

References

  1. IBM Security Bulletin for CVE-2026-123218
    Vendor advisory, affected versions, and fixed release information.

  2. CISA Known Exploited Vulnerabilities entry for CVE-2026-123218
    KEV status, addition date, remediation expectations, and ransomware-use status.

  3. CISA Known Exploited Vulnerabilities Catalog
    Catalog-wide remediation guidance and prioritization context.

  4. NVD record for CVE-2026-123218
    CVE metadata, CVSS information, and record history.

Organizations should consult IBM’s advisory directly for release-specific prerequisites, installation steps, and validation requirements. If an affected Faspex instance cannot be upgraded promptly, treat it as an active exposure: restrict access, preserve relevant evidence, monitor for suspicious administrative activity, and follow incident-response procedures if exploitation is suspected.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

Choosing a tool? Pricing and head-to-head guides

Last verified: 2026-11-13

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.