CVE-2019-17571

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2020-01-06. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 69%
CISA-KEV: Not listedEPSS: 69%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
99.3%
KEV
Not listed

Published

December 20, 2019

Last Modified

May 28, 2026

Advisory Details (9)

Auto-updated Jun 20, 2026
No patch confirmed yet.
generic
https://lists.apache.org/thread.html/r05755112a8c164abc1004bb44f198b1e3d8ca3d546a8f13ebd3aa05f%40%3Cissues.zookeeper.apache.org%3E
generic
https://lists.apache.org/thread.html/eea03d504b36e8f870e8321d908e1def1addda16adda04327fe7c125%40%3Cdev.logging.apache.org%3E
generic
https://lists.apache.org/thread.html/8ab32b4c9f1826f20add7c40be08909de9f58a89dc1de9c09953f5ac%40%3Cissues.activemq.apache.org%3E
generic
https://lists.apache.org/thread.html/752ec92cd1e334a639e79bfbd689a4ec2c6579ec5bb41b53ffdf358d%40%3Cdev.kafka.apache.org%3E
generic
https://lists.apache.org/thread.html/6114ce566200d76e3cc45c521a62c2c5a4eac15738248f58a99f622c%40%3Cissues.activemq.apache.org%3E
generic
https://lists.apache.org/thread.html/564f03b4e9511fcba29c68fc0299372dadbdb002718fa8edcc4325e4%40%3Cjira.kafka.apache.org%3E
generic
https://lists.apache.org/thread.html/479471e6debd608c837b9815b76eab24676657d4444fcfd5ef96d6e6%40%3Cdev.tika.apache.org%3E
generic
https://lists.apache.org/thread.html/44491fb9cc19acc901f7cff34acb7376619f15638439416e3e14761c%40%3Cdev.tika.apache.org%3E
generic
https://lists.apache.org/thread.html/277b4b5c2b0e06a825ccec565fa65bd671f35a4d58e3e2ec5d0618e1%40%3Cdev.tika.apache.org%3E

Vendor Advisories for CVE-2019-17571(9)

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

Patch Availability(20)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuliblog4j1.2-java-doc (1.2.17-8+deb10u1build0.18.04.1) @ bionic2026-05-27ubuntu
ubuntuliblog4j1.2-java (1.2.17-8+deb10u1ubuntu0.2) @ bionic2026-05-27ubuntu
redhatlog4j-0:1.2.14-6.7.el6_102022-06-15redhat
redhatpatch2022-02-10redhat
redhatpatch2022-02-09redhat
redhatpatch2019-06-18redhat
redhatpatch2017-12-07redhat
redhatlog4j-0:1.2.14-19.patch_01.ep5.el62017-12-07redhat
redhatpatch2017-11-16redhat
redhatpatch2017-10-12redhat
redhatpatch2017-10-12redhat
redhatpatch2017-09-26redhat
redhateap7-jboss-ec2-eap-0:7.0.8-1.GA_redhat_1.ep7.el72017-09-26redhat
redhatjboss-ec2-eap-0:7.5.17-1.Final_redhat_4.ep6.el62017-09-05redhat
redhatpatch2017-09-05redhat
redhatlog4j-0:1.2.17-16.el7_42017-08-07redhat
redhattomcat-native-0:1.2.8-10.redhat_10.ep7.el72017-07-25redhat
redhatpatch2017-07-25redhat
mavenlog4j:log4j—ghsa
mavenorg.zenframework.z8.dependencies.commons:log4j-1.2.17—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

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
log4j:log4j1.2.11 ... 1.2.9 (13 versions)——
org.zenframework.z8.dependencies.commons:log4j-1.2.172.0——

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 3× in last 7d / 25× 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.

  1. 2026-07-09 19:06 UTCEPSS rescore
  2. 2026-07-08 15:11 UTCEPSS rescore
  3. 2026-07-07 13:43 UTCEPSS rescore
  4. 2026-07-04 06:28 UTCEPSS rescore
  5. 2026-07-02 14:00 UTCOSV refresh
  6. 2026-07-01 15:03 UTCEPSS rescore
  7. 2026-07-01 15:03 UTCEPSS rescore
  8. 2026-06-30 23:20 UTCEPSS rescore
  9. 2026-06-27 03:06 UTCEPSS rescore
  10. 2026-06-25 13:47 UTCEPSS rescore
  11. 2026-06-25 13:47 UTCEPSS rescore
  12. 2026-06-24 14:03 UTCEPSS rescore
  13. 2026-06-24 14:03 UTCEPSS rescore
  14. 2026-06-23 21:31 UTCEPSS rescore
  15. 2026-06-23 21:30 UTCEPSS rescore
  16. 2026-06-22 14:23 UTCEPSS rescore
  17. 2026-06-18 17:50 UTCEPSS rescore
  18. 2026-06-17 17:50 UTCEPSS rescore
  19. 2026-06-16 17:50 UTCEPSS rescore
  20. 2026-06-15 17:45 UTCEPSS rescore
  21. 2026-06-14 23:15 UTCEPSS rescore
  22. 2026-06-14 23:15 UTCEPSS rescore
  23. 2026-06-14 12:13 UTCOSV refresh
  24. 2026-06-13 22:58 UTCEPSS rescore
  25. 2026-06-12 23:09 UTCEPSS rescore
Show 27 more
  1. 2026-06-11 13:58 UTCEPSS rescore
  2. 2026-06-10 22:16 UTCEPSS rescore
  3. 2026-06-10 13:19 UTCEPSS rescore
  4. 2026-06-07 15:23 UTCEPSS rescore
  5. 2026-06-07 15:23 UTCEPSS rescore
  6. 2026-06-06 13:45 UTCEPSS rescore
  7. 2026-06-06 13:45 UTCEPSS rescore
  8. 2026-06-05 22:45 UTCEPSS rescore
  9. 2026-06-05 22:45 UTCEPSS rescore
  10. 2026-06-04 13:10 UTCEPSS rescore
  11. 2026-06-04 13:10 UTCEPSS rescore
  12. 2026-06-02 20:11 UTCEPSS rescore
  13. 2026-06-02 20:11 UTCEPSS rescore
  14. 2026-05-31 22:29 UTCEPSS rescore
  15. 2026-05-31 22:29 UTCEPSS rescore
  16. 2026-05-31 00:14 UTCEPSS rescore
  17. 2026-05-31 00:14 UTCEPSS rescore
  18. 2026-05-29 13:42 UTCEPSS rescore
  19. 2026-05-28 13:43 UTCEPSS rescore
  20. 2026-05-27 13:38 UTCEPSS rescore
  21. 2026-05-27 10:01 UTCEG score recompute
  22. 2026-05-27 10:01 UTCVendor advisory
  23. 2026-05-27 10:01 UTCGHSA enrichment
  24. 2026-05-26 07:17 UTCEPSS rescore
  25. 2026-05-26 07:17 UTCEPSS rescore
  26. 2026-05-26 07:17 UTCEPSS rescore
  27. 2026-05-25 06:37 UTCOSV refresh

Publicly available exploits

(2 references)

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

  • GitHub PoCHynekPetrak/log4shell-finder
    First seen Dec 14, 2021

    Fastest filesystem scanner for log4shell (CVE-2021-44228, CVE-2021-45046) and other vulnerable (CVE-2017-5645, CVE-2019-17571, CVE-2022-23305, CVE-2022-23307 ... ) instances of log4j library. Excellent performance and low memory footprint.

    Open source ↗
  • GitHub PoCshadow-horse/CVE-2019-17571
    First seen Dec 25, 2019

    Apache Log4j 1.2.X存在反序列化远程代码执行漏洞

    Open source ↗

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

Frequently asked(5)

What is CVE-2019-17571?
CVE-2019-17571 is a critical vulnerability published on December 20, 2019. Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2…
When was CVE-2019-17571 disclosed?
CVE-2019-17571 was first published in the National Vulnerability Database on December 20, 2019, with the most recent update on May 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-17571 actively exploited?
CVE-2019-17571 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-17571?
CVE-2019-17571 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-17571?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-17571, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-17571

Explore →

Is Your Infrastructure Affected by CVE-2019-17571?

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

Start Free Scan →Browse All CVEs