CriticalCVE-2026-123218

    IBM Aspera Faspex Authorization Bypass (CVE-2026-123218)

    Published Last modified In CISA KEV since Sources: EUVD, CVE.org

    Share

    What is affected, what to do

    IBM Aspera Faspex 5.0.0 through 5.0.19 could allow an authorized user to craft a specific message to bypass user authorization and gain full administrative privileges.

    The vulnerability is being actively exploited; treat it as a priority. Update aspera_faspex to version 5.0.19.1. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • IBM Aspera Faspex lte 5.0.0..5.0.19

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    9.8

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    9.8

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: EUVD, CVE.org

    0.5 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 45.7

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    195.70 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    9.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    9.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.5 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    45.7
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 9 November 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-863

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw grants full administrative control of a managed file-transfer platform. That class of system is a favourite target for data-theft and extortion campaigns because it concentrates sensitive partner and customer data in one place. The CVSS vector rates it as network-exploitable with critical impact on confidentiality, integrity and availability. The vendor description does require a valid account, but that is a low bar on portals with many external users. Predicted exploitation likelihood (EPSS) is only moderate and CISA lists no known ransomware use, yet the KEV listing confirms real-world exploitation. Treat internet-facing or externally populated instances as critical and patch them immediately. Internal instances with a small, trusted user base can be patched at high priority in the next maintenance window.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory: Locate every IBM Aspera Faspex instance and check its version. Versions 5.0.0 through 5.0.19 are affected. Handle internet-facing partner and customer portals first.
      • Patch: Upgrade to a fixed Faspex release above 5.0.19. A patch is available from the vendor; look up the exact target version in the IBM Security Bulletin. Snapshot the configuration and database before upgrading so you keep a forensic baseline.
      • Restrict access until patched: Temporarily limit internet access to the Faspex web UI to known partner IP ranges or VPN. Disable self-registration and guest/external accounts where the business can tolerate it.
      • Review privileges: Compare all accounts holding administrative rights against an approved list. Disable any unexpected admin immediately and kill its sessions.
      • Rotate credentials: Renew Faspex admin passwords, API tokens and service-account credentials. Also rotate SMTP, LDAP/SAML bind and storage credentials stored in the Faspex configuration, since a rogue admin could read them.
      • Assess compromise: If you find signs of privilege escalation, open an IR case. Assess NIS2 reporting obligations (24 h early warning), especially if confidential files were exchanged through Faspex.
    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Place Faspex in a dedicated DMZ zone. Expose the administration interface only to a management network or jump host. Publish the FASP transfer channels separately from the web UI.
      • Reverse proxy/WAF: Front Faspex with a reverse proxy. Add rules so that admin and user-management paths are reachable only from admin source IPs. Log, and where feasible block, oversized or structurally anomalous request bodies sent to API endpoints.
      • IAM/least privilege: Reduce Faspex accounts to the minimum and purge stale external users. Enforce SSO with MFA. This does not stop a legitimate user from abusing the flaw, but it sharply cuts the risk from hijacked low-privilege accounts.
      • Host hardening: Run the Faspex service as an unprivileged account. Restrict write access to configuration and web directories. Make sure EDR is active on the host.
      • Data-exfiltration controls: Baseline download volumes from Faspex storage and alert on deviations. Shorten package retention to limit the blast radius.
    3. Runbook step 3

      Detection rules

      • Faspex audit/application logs: Watch for role changes, admin grants, new accounts, and modifications to configuration, SAML/LDAP or the mail relay. Prioritise changes triggered by a non-admin account or made outside change windows.
      • Web server/proxy access logs: Look for standard-user sessions hitting admin endpoints and receiving HTTP 200. Example (SPL): index=proxy host=faspex* uri_path="*admin*" status=200 | stats count by src_ip, user | where NOT user IN (admin_allowlist).
      • EDR process ancestry (Sysmon EID 1 / auditd execve): Alert when the Faspex service or web server process spawns sh, bash, curl, wget, python, powershell.exe or cmd.exe. Sigma shape: ParentImage|contains: faspex AND Image|endswith: [/sh, /bash, cmd.exe, powershell.exe].
      • Network telemetry (Zeek/Suricata): Flag new outbound connections from the Faspex host to unfamiliar destinations, and sudden spikes in download volume to a single external IP.
      • Identity logs: Catch logins by new or reactivated admin accounts from unusual geolocations or ASNs. Correlate IdP logs with Faspex sessions to do this.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    IBM Aspera Faspex 5.0.0 through 5.0.19 could allow an authorized user to craft a specific message to bypass user authorization and gain full administrative privileges.

    Source: ENISA EUVD, NVD (NIST), cvelistv5, CISA KEV Catalog

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    IBMAspera Faspex
    • 5.0.0 – ≤ 5.0.19
    • —
    ibmaspera_faspex
    • 5.0.0 – < 5.0.19.1
    • 5.0.19.1

    Vendors and products

    Weakness classes (CWE)

    • CWE-863Incorrect Authorization

      Class

      The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

      Entry at MITRE CWE-863

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • ibm.comsupport/pages/node/7295921Vendor advisory, Patch, Vendor advisory, euvd
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-1232…government-resource, US government resource

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Initial analysis by NVDNVD

      Show 3 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Product configurationadded
      —
      AND OR *cpe:2.3:a:ibm:aspera_faspex:*:*:*:*:*:*:*:* versions from (including) 5.0.0 up to (excluding) 5.0.19.1 OR cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*
      Reference typeadded
      —
      IBM Corporation: https://www.ibm.com/support/pages/node/7295921 Types: Vendor Advisory
      Reference typeadded
      —
      CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-123218 Types: US Government Resource

      Source identifier: nvd@nist.gov

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: yes

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentremoved
      {"id":"CVE-2026-123218","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-09T20:40:42.498022Z"}
      —
      SSVC assessmentadded
      —
      {"id":"CVE-2026-123218","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-09T00:00:00+00:00"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    3. CISA KEV entry updated9119a7d8…

      4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name

      Show 4 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Date Addedadded
      —
      2026-11-09
      Due Dateadded
      —
      2026-11-09
      Required Actionadded
      —
      2026-11-09
      Vulnerability Nameadded
      —
      2026-11-09

      Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725

    4. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: active, automatable: yes

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-123218
      SSVC assessmentadded
      —
      {"id":"CVE-2026-123218","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-11-09T20:40:42.498022Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    5. ReceivedIBM

      CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

      Weakness type: CWE-863

      Description added or changed

      Show 5 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      IBM Aspera Faspex 5.0.0 through 5.0.19 could allow an authorized user to craft a specific message to bypass user authorization and gain full administrative privileges.
      CVSSadded
      —
      AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
      Weakness type (CWE)added
      —
      CWE-863
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/123xxx/CVE-2026-123218.json">CVE-2026-123218</a>
      Referenceadded
      —
      https://www.ibm.com/support/pages/node/7295921

      Source identifier: psirt@us.ibm.com

    Linked advisories

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-123218
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-123218"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-123218.svg?lang=en" alt="CVE-2026-123218 – NEOSEC Intel" height="20"></a>