Skip to content
Server Security Center
KEVcritical9.8 Used in ransomware campaigns

CVE-2022-47986: IBM Aspera Faspex Code Execution

IBM Aspera Faspex · listed in the CISA catalog of actively exploited vulnerabilities since 2023-02-21.

CVSS v3.1 (CVE record)
9.8
critical
EPSS (exploit probability, 30 days)
>99.9%
among the highest 0.1% of all CVEs
Added to CISA KEV
2023-02-21
US federal due date 2023-03-14
Automatable (CISA SSVC)
yes
technical impact: total

What is CVE-2022-47986?

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.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • IBM Aspera Faspex
    Affected
    • 4.4.2 Patch Level 1 and earlier
    Fixed in
    not stated

    Version statement as published by the CNA (free text).

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: ibm.com/support/pages/node/6952319
  • CISA's deadline for US federal agencies: 2023-03-14 (passed) – a useful benchmark for everyone else, too.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-502 Deserialization of Untrusted Data

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.