Vulnerability

CVE-2022-47986

Critical· 9.8KEVEXPLOITCVSS9.8EPSS94%

.rules3/5

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.

Threat signal

100/100

Severe

Severity

critical

CVSS

9.8

EPSS

94%

Active

KEV

CISA KEV — actively exploited

Ransomware: Known1187d overdue

AffectedIBM — Aspera Faspex

Added to KEV

2023-02-21

Federal patch due (BOD 22-01)

2023-03-14

Required action (CISA verbatim)

Apply updates per vendor instructions.

Vendor advisory + references

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

CVSS

v3.1Open in FIRST calculator →

9.8/ 10CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack VectorNetworkExploitable remotely over the internet — no local access needed.
Attack ComplexityLowNo special conditions — exploit works reliably.
Privileges RequiredNoneUnauthenticated — no credentials needed.
User InteractionNoneFully automated — no victim action needed.
ScopeUnchangedImpact contained to the vulnerable component.
Confidentiality ImpactHighTotal disclosure of sensitive data.
Integrity ImpactHighTotal compromise of integrity — full data modification possible.
Availability ImpactHighTotal loss of availability — full DoS possible.

EPSS

Exploit prediction · 30-day horizonFIRST.org →

94.3%

probability of exploitation in next 30 days

p100

higher than 100% of all CVEs

3-day trend↑ 0pp

Statistically about to be weaponized — top-tier triage urgency.

Vendor VEX

No VEX statements published for CVE-2022-47986. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCAct

Active exploitation with total impact on essential/support systems

exploitation: active
automatable: yes
impact: total
mission: support

Lifecycle

2023-02-21Added to CISA KEVransomware: Known
2023-02-21Public exploit observedexploitdb
2023-02-21Published
2023-03-14Federal patch due (BOD 22-01)
2026-06-12Last modified1 source

No source-event history recorded yet. New revisions will appear here as ingestors re-fetch this CVE.