CVE-2017-17485

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 50% (98th 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: 50%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

FasterXML jackson-databind through 2.8.10 and 2.9.x through 2.9.3 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw. This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper, bypassing a blacklist that is ineffective if the Spring libraries are available in the classpath.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
79
EG Risk 79/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%
Exploitation50% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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
50%
EPSS %ILE
98th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

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

Exploitation none (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 10, 2018

Last Modified

August 27, 2025

Advisory Details (10)

Auto-updated Oct 9, 2026
Patch available. Sources: redhat.
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 6.

https://access.redhat.com/errata/RHSA-2018:1449
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2018:1448
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2018:1447
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 6 and Red Hat JBoss Enterprise Application Platform 7.1.1 for Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2018:0481
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 7.

https://access.redhat.com/errata/RHSA-2018:0480
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 6.

https://access.redhat.com/errata/RHSA-2018:0479
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2018:0478
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2018:0342
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2018:0116
generic

SecurityFocus

http://www.securityfocus.com/archive/1/541652/100/0/threaded

Vendor Advisories for CVE-2017-17485(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatjackson-databind2019-11-14redhat
redhatopenshift3/ose-logging-elasticsearch5:v3.11.153-22019-10-18redhat
redhatopenshift4/ose-logging-elasticsearch5:v4.1.18-2019092019152019-09-27redhat
redhatpatch2019-07-15redhat
redhatresteasy2018-10-16redhat
redhatpicketbox-0:4.1.7-1.Final_redhat_1.1.ep6.el62018-05-14redhat
redhatpicketbox-0:4.1.7-1.Final_redhat_1.1.ep6.el52018-05-14redhat
redhatpicketbox-0:4.1.7-1.Final_redhat_1.1.ep6.el72018-05-14redhat
redhatjboss-ec2-eap-0:7.5.20-1.Final_redhat_1.ep6.el62018-05-14redhat
redhateap7-jboss-ec2-eap-0:7.1.1-3.1.GA_redhat_3.ep7.el72018-03-12redhat
redhateap7-xml-security-0:2.0.9-1.redhat_1.1.ep7.el62018-03-12redhat
redhatpatch2018-03-12redhat
redhateap7-xml-security-0:2.0.9-1.redhat_1.1.ep7.el72018-03-12redhat
redhatrh-maven35-jackson-databind-0:2.7.6-2.4.el72018-02-22redhat
redhatrh-eclipse46-jackson-databind-0:2.6.3-2.6.el72018-01-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 7 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind—
  • every version up to 2.9.4-1: fixed in 2.9.4-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind—
  • every version up to 2.9.4-1: fixed in 2.9.4-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind—
  • every version up to 2.9.4-1: fixed in 2.9.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind—
  • every version up to 2.9.4-1: fixed in 2.9.4-1
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind2.4.2-2, 2.4.2-2+deb8u1, 2.4.2-2+deb8u2
  • every version up to 2.4.2-2+deb8u3: fixed in 2.4.2-2+deb8u3
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind2.8.6-1, 2.8.6-1+deb9u1, 2.8.6-1+deb9u2
  • every version up to 2.8.6-1+deb9u3: fixed in 2.8.6-1+deb9u3
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
com.fasterxml.jackson.core:jackson-databind2.0.0 ... 2.7.9.1 (82 versions)
  • 2.9.0 up to 2.9.4: fixed in 2.9.4
  • 2.8.0 up to 2.8.11: fixed in 2.8.11
  • every version up to 2.7.9.2: fixed in 2.7.9.2
—

Weakness Classification(1)

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

Additional Vendor Advisories

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 19× 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 112 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCAl1ex/CVE-2017-17485
    First seen May 22, 2020

    CVE-2017-17485:Jackson-databind RCE

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2017-17485?
CVE-2017-17485 is a critical vulnerability published on January 10, 2018. FasterXML jackson-databind through 2.8.10 and 2.9.x through 2.9.3 allows unauthenticated remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization flaw. This is exploitable by sending maliciously crafted JSON input to the readValue method of the ObjectMapper,…
When was CVE-2017-17485 disclosed?
CVE-2017-17485 was first published on January 10, 2018, with the most recent update on August 27, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-17485 actively exploited?
CVE-2017-17485 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 50% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-17485?
CVE-2017-17485 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-17485?
A fix for CVE-2017-17485 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-17485 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-17485?

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

Book a Demo →Browse All CVEs