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% (93rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.5 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2020-05-15) is not newer than that change (2026-10-08), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2020-0420 (ENISA EUVD) · GHSA-cf6r-3wgc-h863 (GitHub Security Advisories)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
93rd
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-11-12). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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 Nov 8, 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(8)

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
mavencom.fasterxml.jackson.core:jackson-databind @ 2.6.7.3 (fixes <= 2.6.7.2)—ghsa
mavencom.fasterxml.jackson.core:jackson-databind @ 2.9.10 (fixes >= 2.9.0, < 2.9.10)—ghsa
mavencom.fasterxml.jackson.core:jackson-databind @ 2.8.11.5 (fixes >= 2.7.0, <= 2.8.11.4)—ghsa

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 / 72× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 274 rows 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 174 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 01:48 UTCEchelonGraph re-scored
  2. 2026-11-13 01:48 UTCVendor advisory
  3. 2026-11-13 01:48 UTCGHSA enrichmentGHSA-cf6r-3wgc-h863 · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-12 16:28 UTCEPSS rescoreEPSS 5.6% · 93rd percentile
  5. 2026-11-12 02:17 UTCEchelonGraph re-scored
  6. 2026-11-12 02:17 UTCVendor advisory
  7. 2026-11-12 02:17 UTCGHSA enrichmentGHSA-cf6r-3wgc-h863 · GitHub severity HIGH · GitHub CVSS 7.5
  8. 2026-11-11 16:30 UTCEPSS rescoreEPSS 5.6% · 93rd percentile
  9. 2026-11-11 02:45 UTCEchelonGraph re-scored
  10. 2026-11-11 02:45 UTCGHSA enrichmentGHSA-cf6r-3wgc-h863 · GitHub severity HIGH · GitHub CVSS 7.5
  11. 2026-11-10 16:33 UTCEPSS rescoreEPSS 5.6% · 93rd percentile
  12. 2026-11-10 02:54 UTCEchelonGraph re-scored
  13. 2026-11-10 02:54 UTCVendor advisory
  14. 2026-11-10 02:54 UTCGHSA enrichmentGHSA-cf6r-3wgc-h863 · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-11-09 16:28 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  16. 2026-11-09 03:23 UTCEchelonGraph re-scored
  17. 2026-11-09 03:23 UTCVendor advisory
  18. 2026-11-09 03:23 UTCGHSA enrichmentGHSA-cf6r-3wgc-h863 · GitHub severity HIGH · GitHub CVSS 7.5
  19. 2026-11-08 16:31 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  20. 2026-11-08 03:53 UTCEchelonGraph re-scored
  21. 2026-11-08 03:53 UTCVendor advisory
  22. 2026-11-08 03:53 UTCGHSA enrichmentGHSA-cf6r-3wgc-h863 · GitHub severity HIGH · GitHub CVSS 7.5
  23. 2026-11-07 16:32 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  24. 2026-11-07 04:22 UTCEchelonGraph re-scored
  25. 2026-11-07 04:22 UTCVendor advisory
Show 75 more
  1. 2026-11-07 04:22 UTCGHSA enrichmentGHSA-cf6r-3wgc-h863 · GitHub severity HIGH · GitHub CVSS 7.5
  2. 2026-11-06 16:29 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  3. 2026-11-06 04:47 UTCEchelonGraph re-scored
  4. 2026-11-06 04:47 UTCVendor advisory
  5. 2026-11-06 04:47 UTCGHSA enrichmentGHSA-cf6r-3wgc-h863 · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-05 16:28 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  7. 2026-11-05 05:17 UTCEchelonGraph re-scored
  8. 2026-11-05 05:17 UTCVendor advisory
  9. 2026-11-05 05:17 UTCGHSA enrichmentGHSA-cf6r-3wgc-h863 · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-11-04 16:28 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  11. 2026-11-04 05:46 UTCEchelonGraph re-scored
  12. 2026-11-04 05:46 UTCVendor advisory
  13. 2026-11-04 05:46 UTCGHSA enrichmentGHSA-cf6r-3wgc-h863 · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-11-03 16:35 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  15. 2026-11-03 06:15 UTCEchelonGraph re-scored
  16. 2026-11-03 06:15 UTCVendor advisory
  17. 2026-11-03 06:15 UTCGHSA enrichmentGHSA-cf6r-3wgc-h863 · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-11-03 02:55 UTCOSV refresh
  19. 2026-11-02 16:35 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  20. 2026-11-02 06:42 UTCEchelonGraph re-scored
  21. 2026-11-02 06:42 UTCVendor advisory
  22. 2026-11-02 06:42 UTCGHSA enrichmentGHSA-cf6r-3wgc-h863 · GitHub severity HIGH · GitHub CVSS 7.5
  23. 2026-11-01 16:28 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  24. 2026-11-01 08:40 UTCGHSA enrichmentGHSA-cf6r-3wgc-h863 · GitHub severity HIGH · GitHub CVSS 7.5
  25. 2026-11-01 08:40 UTCEchelonGraph re-scored
  26. 2026-11-01 07:12 UTCEchelonGraph re-scored
  27. 2026-11-01 07:12 UTCVendor advisory
  28. 2026-10-31 16:27 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  29. 2026-10-31 07:39 UTCEchelonGraph re-scored
  30. 2026-10-31 07:39 UTCVendor advisory
  31. 2026-10-30 16:28 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  32. 2026-10-30 08:09 UTCEchelonGraph re-scored
  33. 2026-10-30 08:09 UTCVendor advisory
  34. 2026-10-29 16:28 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  35. 2026-10-29 08:38 UTCEchelonGraph re-scored
  36. 2026-10-29 08:38 UTCVendor advisory
  37. 2026-10-28 16:27 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  38. 2026-10-28 09:07 UTCEchelonGraph re-scored
  39. 2026-10-28 09:07 UTCVendor advisory
  40. 2026-10-27 16:27 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  41. 2026-10-27 09:02 UTCEchelonGraph re-scored
  42. 2026-10-27 09:02 UTCVendor advisory
  43. 2026-10-26 16:27 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  44. 2026-10-26 08:21 UTCVendor advisory
  45. 2026-10-25 19:07 UTCEchelonGraph re-scored
  46. 2026-10-25 16:27 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  47. 2026-10-25 08:50 UTCEchelonGraph re-scored
  48. 2026-10-25 08:50 UTCVendor advisory
  49. 2026-10-24 16:28 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  50. 2026-10-24 09:19 UTCEchelonGraph re-scored
  51. 2026-10-23 16:27 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  52. 2026-10-23 09:48 UTCEchelonGraph re-scored
  53. 2026-10-23 09:48 UTCVendor advisory
  54. 2026-10-22 16:28 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  55. 2026-10-22 10:14 UTCEchelonGraph re-scored
  56. 2026-10-22 10:14 UTCVendor advisory
  57. 2026-10-21 16:27 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  58. 2026-10-21 10:40 UTCEchelonGraph re-scored
  59. 2026-10-21 10:40 UTCVendor advisory
  60. 2026-10-20 16:27 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  61. 2026-10-20 11:09 UTCEchelonGraph re-scored
  62. 2026-10-20 11:09 UTCVendor advisory
  63. 2026-10-19 16:27 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  64. 2026-10-19 11:38 UTCEchelonGraph re-scored
  65. 2026-10-19 11:38 UTCVendor advisory
  66. 2026-10-18 16:27 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  67. 2026-10-18 09:29 UTCEchelonGraph re-scored
  68. 2026-10-18 09:29 UTCVendor advisory
  69. 2026-10-17 16:28 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  70. 2026-10-17 09:57 UTCEchelonGraph re-scored
  71. 2026-10-17 09:57 UTCVendor advisory
  72. 2026-10-16 16:31 UTCEPSS rescoreEPSS 5.6% · 92nd percentile
  73. 2026-10-16 10:25 UTCEchelonGraph re-scored
  74. 2026-10-16 10:25 UTCVendor advisory
  75. 2026-10-15 16:27 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 (93rd 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.