# CVE-2022-47986: IBM Aspera Faspex Code Execution

> Remote attackers can execute arbitrary code on IBM Aspera Faspex servers via a YAML deserialization flaw in an obsolete API call.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 21 Feb 2023 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-3w56-qhmc-wqwr

## What is CVE-2022-47986?

CVE-2022-47986 is a critical unsafe deserialization vulnerability in IBM Aspera Faspex, published on 17 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2022-47986?

It affects 1 product.


Products: Ibm Aspera Faspex.

## How do I fix CVE-2022-47986?

No fix has been published for CVE-2022-47986 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 14 Mar 2023.

## Is CVE-2022-47986 being exploited?

Yes. Attackers have exploited CVE-2022-47986 in the wild since at least 21 Feb 2023, including in ransomware campaigns.

Public exploit code:

- Aspera Faspex Pre Auth RCE (github_poc): https://github.com/ohnonoyesyes/CVE-2022-47986
- CVE-2022-47986: Python, Ruby, NMAP and Metasploit modules to exploit the vulnerability. (github_poc): https://github.com/mauricelambert/CVE-2022-47986
- IBM Aspera Faspex 4.4.1 - YAML deserialization (RCE) (exploitdb)
- IBM Aspera Faspex <=4.4.2 PL1 - Remote Code Execution (nuclei): http/cves/2022/CVE-2022-47986.yaml

## Other vulnerabilities in IBM Aspera Faspex

- [CVE-2023-27874](https://insights.sbomify.com/CVE-2023-27874/): IBM Aspera Faspex XML external entity injection (critical 9.9)
- [CVE-2026-14958](https://insights.sbomify.com/CVE-2026-14958/): OS command injection in IBM Aspera Faspex (critical 9.1)
- [CVE-2026-14959](https://insights.sbomify.com/CVE-2026-14959/): OS Command Injection in IBM Aspera Faspex (critical 9.1)
- [CVE-2026-14996](https://insights.sbomify.com/CVE-2026-14996/): Multiple vulnerabilities in IBM Aspera Faspex (high 8.2)
- [CVE-2023-37400](https://insights.sbomify.com/CVE-2023-37400/): IBM Aspera Faspex privilege escalation (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-47986 and fix it if it is affected.

What it is: CVE-2022-47986 is a critical unsafe deserialization vulnerability in IBM Aspera Faspex, published on 17 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-47986 in the wild since at least 21 Feb 2023, including in ransomware campaigns.

Affected product: IBM Aspera Faspex. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-47986/ (Markdown: https://insights.sbomify.com/CVE-2022-47986/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-47986
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-47986
- OSV: https://osv.dev/vulnerability/CVE-2022-47986

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-47986/
Summaries are generated and may contain mistakes; the official description above is the record.