+44 1865 950 828 Secure Your Business
Actively exploitedKnown ransomware use

CVE-2022-47986 IBM Aspera Faspex Code Execution Vulnerability

IBM Aspera Faspex could allow a remote attacker to execute code on the system, caused by a YAML deserialization flaw.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch nowCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 21 Feb 2023.
  • CISA lists it as known to be used in ransomware campaigns.
  • Rated Critical severity (CVSS 9.8, scored by Vendor).
  • It has been in the catalogue for 1,354 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

IBM Aspera Faspex 4.4.2 Patch Level 1 and earlier could allow a remote attacker to execute arbitrary code on the system, caused by a YAML deserialization flaw. By sending a specially crafted obsolete API call, an attacker could exploit this vulnerability to execute arbitrary code on the system. The obsolete API call was removed in Faspex 4.4.2 PL2. IBM X-Force ID: 243512.

Affected Versions

ProductVersions
IBM Aspera Faspex4.4.2 Patch Level 1 and earlier

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for IBM Aspera Faspex. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply updates per vendor instructions.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Vendor Advisories

Regulation

The Compliance Clock

Cyber EssentialsRated critical, so if it affects devices in your Cyber Essentials scope, the update must be installed within 14 days of the vendor releasing it.NIS2If exploitation causes a significant incident, essential and important entities owe their CSIRT an early warning within 24 hours and a notification within 72 hours.DORAFinancial entities must classify ICT incidents and send an initial notification for a major incident within strict deadlines, with exploited flaws a common cause.US federal (BOD 22-01)Federal civilian agencies had until 14 Mar 2023 to remediate. A sensible benchmark for everyone else.

General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.

Stay Ahead

More Exploited IBM Flaws

Get alerts for IBMWe email you when a new IBM vulnerability is confirmed as exploited. Add more vendors on Threat Watch.

By signing up you agree to receive Threat Watch alerts. Unsubscribe at any time. See our Privacy Policy.

CVE-2026-9198IBM Langflow Code Injection VulnerabilityAdded 4 Aug 2026CVE-2013-3993 · RansomwareIBM InfoSphere BigInsights Invalid Input VulnerabilityAdded 25 May 2022CVE-2015-7450IBM WebSphere Application Server and Server Hypervisor Edition Code Injection.Added 10 Jan 2022CVE-2020-4430IBM Data Risk Manager Directory Traversal VulnerabilityAdded 3 Nov 2021CVE-2020-4427IBM Data Risk Manager Security Bypass VulnerabilityAdded 3 Nov 2021CVE-2020-4428IBM Data Risk Manager Remote Code Execution VulnerabilityAdded 3 Nov 2021

All 8 exploited IBM vulnerabilities

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2022-47986 and every other exploited flaw on the list.

Check My Exposure
Evidence

Sources

  1. CISA Known Exploited Vulnerabilities catalogue
  2. NVD: CVE-2022-47986
  3. CVE record: CVE-2022-47986
  4. FIRST EPSS
  5. exchange.xforce.ibmcloud.com/vulnerabilities/243512?_ga=2.189195179.1800390251.1676559338-700333034.
  6. ibm.com/support/pages/node/6952319
  7. exchange.xforce.ibmcloud.com/vulnerabilities/243512
  8. packetstormsecurity.com/files/171772/IBM-Aspera-Faspex-4.4.1-YAML-Deserialization.html