CVE-2017-3066
Adobe ColdFusion 2016 Update 3 and earlier, ColdFusion 11 update 11 and earlier, ColdFusion 10 Update 22 and earlier have a Java deserialization vulnerability in the Apache BlazeDS library. Successful exploitation could lead to arbitrary code execution.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. Insecure deserialization payloads can be built from many different gadget chains, so WAF signatures only catch the known ones.
Also consider: allow-list classes · patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2017-3066 being exploited?
Yes. CVE-2017-3066 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2017-3066?
CVE-2017-3066 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2017-3066?
Yes. A fix has been recorded for CVE-2017-3066. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2017-3066 affect?
CVE-2017-3066 affects adobe:coldfusion. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affectedAdobe ColdFusion ColdFusion 2016 Update 3 and earlier, ColdFusion 11 update 11 and earlier, ColdFusion 10 Update 22 and earlier
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Public exploit code: 1 on Exploit-DB · 2 GitHub proofs of concept
- codewhitesec/ColdFusionPwn · 95 ★
- cucadili/CVE-2017-3066 · 2 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- total
Assessed by CISA 24 Feb 2025 (SSVC 2.0.3).
timeline
- 27 Apr 2017Published
- 7 Feb 2018First public exploit or proof of concept · 285 days (about 10 months) later
- 24 Feb 2025Added to CISA KEV (exploited in the wild) · 2,574 days (about 7 years) later
- 24 Feb 2025CISA SSVC assessment: exploitation active · 1 day later
- 17 Mar 2025CISA remediation due date (US federal agencies) · 20 days later
- 21 Oct 2025CVE record last updated · 219 days (about 7 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Exploitexploit-db.com /exploits/43993/
- Linkhelpx.adobe.com /security/products/coldfusion/apsb17-14.html
- Linksecurityfocus.com /bid/98003
- Linksecuritytracker.com /id/1038364
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2017-3066
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Exploit-DB: published exploits
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.