CVE-2017-20189

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.3% (69th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

In Clojure before 1.9.0, classes can be used to construct a serialized object that executes arbitrary code upon deserialization. This is relevant if a server deserializes untrusted objects.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.3%
EPSS %ILE
70th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

January 22, 2024

Last Modified

November 3, 2025

Advisory Details (6)

Auto-updated Oct 9, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: github_commit, github_pr.
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20241108-0002/
generic

Vulnerability Details - Clojure Command Injection by Deserialization - HackMD

https://hackmd.io/%40fe1w0/HyefvRQKp
github_pr Patch Available

Add a gadget chain for exploiting the presence of clojure.

Patch available: frohoff/ysoserial v0.0.6 (PR #68 merged 2017-07-19)

https://github.com/frohoff/ysoserial/pull/68/files
github_commit

commit 271674c9b484 (clojure/clojure)

Fix landed in clojure/clojure commit 271674c9b484 — awaiting tagged release

https://github.com/clojure/clojure/commit/271674c9b484d798484d134a5ac40a6df15d3ac3
generic

Jira

https://clojure.atlassian.net/browse/CLJ-2204
generic🔴 Active Exploitation

Deserialization of Untrusted Data in org.clojure:clojure | CVE-2017-20189 | Snyk

https://security.snyk.io/vuln/SNYK-JAVA-ORGCLOJURE-5740378

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
clojure—
  • every version up to 1.9.0-1: fixed in 1.9.0-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
clojure—
  • every version up to 1.9.0-1: fixed in 1.9.0-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
clojure—
  • every version up to 1.9.0-1: fixed in 1.9.0-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
clojure—
  • every version up to 1.9.0-1: fixed in 1.9.0-1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.clojure:clojure1.0.0 ... 1.9.0-beta4 (115 versions)
  • every version up to 1.9.0: fixed in 1.9.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 144 total refreshes for this CVE.

  1. 2026-10-10 19:55 UTCEPSS rescore
  2. 2026-10-09 20:02 UTCEPSS rescore
  3. 2026-10-08 16:36 UTCEPSS rescore
  4. 2026-10-07 23:41 UTCEPSS rescore
  5. 2026-10-06 15:12 UTCEPSS rescore
  6. 2026-10-05 17:38 UTCEPSS rescore
  7. 2026-10-04 23:18 UTCEPSS rescore
  8. 2026-10-03 14:21 UTCEPSS rescore
  9. 2026-09-30 14:59 UTCEPSS rescore
  10. 2026-09-30 09:32 UTCEG score recompute
  11. 2026-09-28 13:45 UTCEPSS rescore
  12. 2026-09-27 13:40 UTCEPSS rescore
  13. 2026-09-27 13:40 UTCEPSS rescore
  14. 2026-09-26 15:53 UTCEPSS rescore
  15. 2026-09-24 13:59 UTCEPSS rescore
  16. 2026-09-22 10:45 UTCOSV refresh
  17. 2026-09-18 19:22 UTCEPSS rescore
  18. 2026-09-17 19:22 UTCEPSS rescore
  19. 2026-09-15 03:05 UTCEPSS rescore
  20. 2026-09-15 03:05 UTCEPSS rescore
  21. 2026-09-13 16:42 UTCEPSS rescore
  22. 2026-09-12 14:55 UTCEPSS rescore
  23. 2026-09-11 09:31 UTCEPSS rescore
  24. 2026-09-07 15:56 UTCEPSS rescore
  25. 2026-09-06 13:43 UTCEPSS rescore
Show 75 more
  1. 2026-09-05 15:23 UTCEPSS rescore
  2. 2026-09-04 13:56 UTCEPSS rescore
  3. 2026-09-03 07:30 UTCOSV refresh
  4. 2026-09-02 14:07 UTCEPSS rescore
  5. 2026-09-02 14:07 UTCEPSS rescore
  6. 2026-09-01 03:31 UTCEPSS rescore
  7. 2026-08-30 19:13 UTCEPSS rescore
  8. 2026-08-27 14:21 UTCEPSS rescore
  9. 2026-08-26 14:41 UTCEPSS rescore
  10. 2026-08-25 13:44 UTCEPSS rescore
  11. 2026-08-21 23:44 UTCEPSS rescore
  12. 2026-08-20 22:51 UTCEPSS rescore
  13. 2026-08-19 16:59 UTCEPSS rescore
  14. 2026-08-18 13:43 UTCEPSS rescore
  15. 2026-08-17 13:42 UTCEPSS rescore
  16. 2026-08-16 20:56 UTCOSV refresh
  17. 2026-08-16 14:51 UTCEPSS rescore
  18. 2026-08-16 02:10 UTCEPSS rescore
  19. 2026-08-15 01:26 UTCEPSS rescore
  20. 2026-08-12 13:46 UTCEPSS rescore
  21. 2026-08-09 13:42 UTCEPSS rescore
  22. 2026-08-07 16:22 UTCEPSS rescore
  23. 2026-08-06 13:42 UTCEPSS rescore
  24. 2026-08-05 19:12 UTCEPSS rescore
  25. 2026-08-04 15:05 UTCEPSS rescore
  26. 2026-08-02 02:23 UTCEPSS rescore
  27. 2026-08-01 14:36 UTCOSV refresh
  28. 2026-08-01 04:11 UTCEPSS rescore
  29. 2026-07-30 16:24 UTCEPSS rescore
  30. 2026-07-30 01:26 UTCEPSS rescore
  31. 2026-07-28 15:32 UTCEPSS rescore
  32. 2026-07-26 14:51 UTCEPSS rescore
  33. 2026-07-23 14:15 UTCEPSS rescore
  34. 2026-07-23 01:28 UTCEG score recompute
  35. 2026-07-22 22:08 UTCEG score recompute
  36. 2026-07-22 14:04 UTCEPSS rescore
  37. 2026-07-22 14:04 UTCEPSS rescore
  38. 2026-07-21 15:21 UTCEPSS rescore
  39. 2026-07-21 15:21 UTCEPSS rescore
  40. 2026-07-20 17:04 UTCEPSS rescore
  41. 2026-07-19 14:28 UTCEPSS rescore
  42. 2026-07-19 14:28 UTCEPSS rescore
  43. 2026-07-19 02:26 UTCEPSS rescore
  44. 2026-07-19 02:26 UTCEPSS rescore
  45. 2026-07-18 10:00 UTCEPSS rescore
  46. 2026-07-16 16:59 UTCEPSS rescore
  47. 2026-07-16 16:59 UTCEPSS rescore
  48. 2026-07-15 16:54 UTCEPSS rescore
  49. 2026-07-15 01:56 UTCEPSS rescore
  50. 2026-07-15 01:56 UTCEPSS rescore
  51. 2026-07-14 21:40 UTCOSV refresh
  52. 2026-07-13 22:26 UTCEPSS rescore
  53. 2026-07-12 05:43 UTCEPSS rescore
  54. 2026-07-11 08:24 UTCEPSS rescore
  55. 2026-07-09 19:06 UTCEPSS rescore
  56. 2026-07-08 15:10 UTCEPSS rescore
  57. 2026-07-06 16:24 UTCEPSS rescore
  58. 2026-07-06 16:24 UTCEPSS rescore
  59. 2026-07-06 02:20 UTCEPSS rescore
  60. 2026-07-06 02:20 UTCEPSS rescore
  61. 2026-07-05 02:27 UTCEPSS rescore
  62. 2026-07-04 06:28 UTCEPSS rescore
  63. 2026-07-02 16:54 UTCEPSS rescore
  64. 2026-07-01 15:02 UTCEPSS rescore
  65. 2026-06-30 23:19 UTCEPSS rescore
  66. 2026-06-30 23:19 UTCEPSS rescore
  67. 2026-06-29 14:03 UTCEPSS rescore
  68. 2026-06-28 14:04 UTCEPSS rescore
  69. 2026-06-28 04:53 UTCEPSS rescore
  70. 2026-06-27 03:06 UTCEPSS rescore
  71. 2026-06-27 03:05 UTCEPSS rescore
  72. 2026-06-26 22:37 UTCOSV refresh
  73. 2026-06-25 13:47 UTCEPSS rescore
  74. 2026-06-24 14:02 UTCEPSS rescore
  75. 2026-06-24 14:02 UTCEPSS rescore

Related CVEs(same product + same CWE)

Same product

1 shown

Debian:11:clojure

Frequently asked(5)

What is CVE-2017-20189?
CVE-2017-20189 is a critical vulnerability published on January 22, 2024. In Clojure before 1.9.0, classes can be used to construct a serialized object that executes arbitrary code upon deserialization. This is relevant if a server deserializes untrusted objects.
When was CVE-2017-20189 disclosed?
CVE-2017-20189 was first published on January 22, 2024, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-20189 actively exploited?
CVE-2017-20189 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (70th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-20189?
CVE-2017-20189 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-20189?
A fix for CVE-2017-20189 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-20189

Explore →

Is Your Infrastructure Affected by CVE-2017-20189?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs