CVE-2019-14892

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 5.6% (92nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2020-0420 (ENISA EUVD)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 5.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was discovered in jackson-databind in versions before 2.9.10, 2.8.11.5 and 2.6.7.3, where it would permit polymorphic deserialization of a malicious object using commons-configuration 1 and 2 JNDI classes. An attacker could use this flaw to execute arbitrary code.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
61
EG Risk 61/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation5.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
5.6%
EPSS %ILE
92nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
5.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 2, 2020

Last Modified

October 8, 2026

Advisory Details (6)

Auto-updated Oct 23, 2026
Patch available. Sources: redhat.
Web page

Block two more gadget types (commons-configuration/-2) · Issue #2462 · FasterXML/jackson-databind · GitHub

https://github.com/FasterXML/jackson-databind/issues/2462
Red HatMentions a patch (unverified)

1758171 – (CVE-2019-14892) CVE-2019-14892 jackson-databind: Serialization gadgets in classes of the commons-configuration package

https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14892
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2020:0729

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatjackson-databind2020-07-28redhat
redhatpatch2020-05-18redhat
redhateap7-wildfly-transaction-client-0:1.1.8-1.Final_redhat_00001.1.el8eap2020-01-21redhat
redhateap7-wildfly-transaction-client-0:1.1.8-1.Final_redhat_00001.1.el6eap2020-01-21redhat
redhateap7-wildfly-transaction-client-0:1.1.8-1.Final_redhat_00001.1.el7eap2020-01-21redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind—
  • every version up to 2.10.0-1: fixed in 2.10.0-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind—
  • every version up to 2.10.0-1: fixed in 2.10.0-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind—
  • every version up to 2.10.0-1: fixed in 2.10.0-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jackson-databind—
  • every version up to 2.10.0-1: fixed in 2.10.0-1
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
com.fasterxml.jackson.core:jackson-databind2.9.0 ... 2.9.9.3 (17 versions)
  • every version up to 2.6.7.3: fixed in 2.6.7.3
  • 2.7.0 up to 2.8.11.5: fixed in 2.8.11.5
  • 2.9.0 up to 2.9.10: fixed in 2.9.10
—

Weakness Classification(2)

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

Additional Vendor Advisories

(2)

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 20× in last 7d / 64× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 218 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 118 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2019-14892?
CVE-2019-14892 is a critical-severity vulnerability; its CVE record was published on March 2, 2020. A flaw was discovered in jackson-databind in versions before 2.9.10, 2.8.11.5 and 2.6.7.3, where it would permit polymorphic deserialization of a malicious object using commons-configuration 1 and 2 JNDI classes. An attacker could use this flaw to execute arbitrary code.
When was the CVE record for CVE-2019-14892 published?
The CVE record for CVE-2019-14892 was published on March 2, 2020. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2019-14892 actively exploited?
CVE-2019-14892 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.6% probability of exploitation in the next 30 days (92nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-14892?
CVE-2019-14892 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-14892?
A fix for CVE-2019-14892 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-14892 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-2019-14892

Explore →

Is Your Infrastructure Affected by CVE-2019-14892?

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