Threats / Adobe / CVE-2009-3960
CVE-2009-3960
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Adobe BlazeDS vulnerability
Adobe BlazeDS contains an information disclosure vulnerability affecting LifeCycle and ColdFusion deployments. The flaw has been exploited in the wild and associated with ransomware campaigns.
Verdict
Today item, not a backlog item.
Active exploitation and ransomware association indicate this vulnerability poses significant risk to affected Adobe product users. High EPSS score reflects widespread attack potential despite unavailable CVSS metrics.
CISA KEV Yes · 2022-03-074Ransomware use Flagged4EPSS 0.90012 (verify live)5CVSS 6.5 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: partial3Exploit Public PoC / detection · Metasploit module11
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
15 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 2022-03-07), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.90012 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) · Affected: Adobe, BlazeDS. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: partialCISA'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 4403 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: Metasploit module. 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 exploit the information disclosure flaw in BlazeDS to extract sensitive data from the target system.
Business
Confidential business information, customer data, or system credentials are compromised, creating compliance violations and breach notification obligations.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I use disclosed information to escalate privileges or pivot to deploy ransomware across the infrastructure.
Business
Systems become encrypted and unavailable, halting operations and forcing costly recovery or ransom decisions.
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
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by adobeCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.