Aspera Faspex
Auto-added after CISA flagged Aspera Faspex as actively exploited (KEV catalog). Version and lifecycle mapping is pending review, so this is assessed at the product level and is never reported as a confident "healthy".
Known exploited vulnerability
CISA's Known Exploited Vulnerabilities (KEV) catalog flagged Aspera Faspex (IBM) as exploited in the wild — that's why IsItPatched started tracking it. The vulnerability that triggered it:
CVE-2022-47986 ↗ view on NVD
Per-version vulnerability and lifecycle data for Aspera Faspex is still being mapped, so no health score is shown yet. Treat it as urgent: identify the exact version you run and confirm it against IBM's advisory, then move to a patched, supported release.
Summary iPlain-English security verdict for Aspera Faspex, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
Aspera Faspex is on CISA's Known Exploited Vulnerabilities (KEV) catalog — it was confirmed under active attack in the wild, which is why CVE-2022-47986 led IsItPatched to start tracking IBM's Aspera Faspex. Its per-version vulnerability and lifecycle data is still being mapped, so no health score is shown yet. Treat Aspera Faspex as urgent: identify the exact version you run and confirm it against IBM's security advisory, then move to a patched, supported release.
Disclosure trend iNew CVEs published for Aspera Faspex each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
No urgent unpatched issues identified. ✓
Get alerted about Aspera Faspex
Be emailed the moment Aspera Faspex gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for Aspera Faspex — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is Aspera Faspex safe and patched?
Aspera Faspex is on CISA's Known Exploited Vulnerabilities (KEV) catalog — it was confirmed under active attack in the wild, which is why CVE-2022-47986 led IsItPatched to start tracking IBM's Aspera Faspex. Its per-version vulnerability and lifecycle data is still being mapped, so no health score is shown yet. Treat Aspera Faspex as urgent: identify the exact version you run and confirm it against IBM's security advisory, then move to a patched, supported release.
What should I do about Aspera Faspex now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against IBM's official advisory.
Why is Aspera Faspex listed on IsItPatched?
Aspera Faspex was added automatically because CISA's Known Exploited Vulnerabilities (KEV) catalog flagged it as actively exploited in the wild. IsItPatched tracks its known CVEs, severity (CVSS), exploitation probability (EPSS) and KEV status from public data; its version and lifecycle mapping is verified over time.
Has Aspera Faspex been actively exploited?
Yes. CISA added Aspera Faspex to its Known Exploited Vulnerabilities (KEV) catalog after confirming exploitation in the wild — the triggering vulnerability is CVE-2022-47986. Make sure you are running a patched, supported version of Aspera Faspex and confirm it against IBM's security advisory.
Similar software we track
More from IBM tracked on IsItPatched.
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against IBM's official advisory before you patch or upgrade.