Threats / IBM / CVE-2022-47986
CVE-2022-47986
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
IBM Aspera Faspex vulnerability
IBM Aspera Faspex contains a YAML deserialization vulnerability allowing remote code execution. The flaw has been exploited in the wild and leveraged in ransomware campaigns.
Verdict
Today item, not a backlog item.
A critical remote code execution vulnerability in IBM Aspera Faspex via unsafe YAML deserialization enables unauthenticated attackers to execute arbitrary code. Active exploitation and ransomware deployment confirm severe real-world risk.
CISA KEV Yes · 2023-02-215Ransomware use Flagged5EPSS 0.99968 (verify live)6Exploit Weaponized · public PoC7CVSS 9.83CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
580 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-02-21), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99968 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: IBM, Aspera Faspex. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-502 Deserialization of Untrusted Data — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 4 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious YAML payload and send it to the vulnerable Faspex endpoint to trigger deserialization.
Business
Attacker gains code execution on the Faspex server with application privileges.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I establish persistence and move laterally within the network to identify high-value targets and sensitive data.
Business
Attacker expands foothold across infrastructure, accessing confidential files and systems.
3
Lateral reach — past segmentation narrative 3
Attacker
I deploy ransomware across compromised systems to encrypt critical business data and demand payment.
Business
Operations halt, data becomes inaccessible, and the organization faces extortion and potential data breach disclosure.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05