BlazeDS
Auto-added after CISA flagged BlazeDS 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".
Summary iPlain-English security verdict for BlazeDS, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
BlazeDS currently scores 20/100 — critical, with active exploitation. 1 of its known vulnerability is being actively exploited in the wild (CISA KEV), including CVE-2009-3960. Upgrade immediately and review your exposure to the actively-exploited CVEs below.
The known vulnerabilities
IsItPatched tracks 1 known vulnerability in Adobe BlazeDS disclosed in 2010. CVE-2009-3960 is a medium-severity vulnerability (CVSS 6.5), which is actively exploited in the wild (CISA KEV). Move to a patched, supported release — this issue is being exploited in the wild, so treat it as urgent.
Disclosure trend iNew CVEs published for BlazeDS each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
1 of its known vulnerability is linked to ransomware campaigns (CISA KEV).
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.
Most urgent first — actively exploited, then likeliest to be exploited.
CVE-2009-3960 MEDIUM exploited ransomware EPSS 90% → see advisoryGet alerted about BlazeDS
Be emailed the moment BlazeDS 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 BlazeDS — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is BlazeDS safe and patched?
BlazeDS currently scores 20/100 — critical, with active exploitation. 1 of its known vulnerability is being actively exploited in the wild (CISA KEV), including CVE-2009-3960. Upgrade immediately and review your exposure to the actively-exploited CVEs below.
What should I do about BlazeDS now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against Adobe's official advisory. Some issues are under active exploitation, so treat this as urgent.
Why is BlazeDS listed on IsItPatched?
BlazeDS 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 BlazeDS been actively exploited?
Yes. CISA added BlazeDS to its Known Exploited Vulnerabilities (KEV) catalog after confirming exploitation in the wild — the triggering vulnerability is CVE-2009-3960. Make sure you are running a patched, supported version of BlazeDS and confirm it against Adobe's security advisory.
Similar software we track
More from Adobe tracked on IsItPatched.
lifecycle unknown — needs latest supported version
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against Adobe's official advisory before you patch or upgrade.