CVE-2019-17558

CRITICALNVD 7.59.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.5 retained for reference. The 9.0 is the floor for confirmed exploitation, not an impact rating: this CVE's impact severity (EG Severity) is CVSS 7.5 HIGH under GitHub Security Advisory CVSS. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2020-0320 (ENISA EUVD) · GHSA-ww97-9w65-2crx (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 99%CVSS: 7.5Exploit: Metasploit · Exploit-DB (verified) · other public PoCExposed services: Not assessed

A fix is available — apply it.

Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter. A Velocity template can be provided through Velocity templates in a configset velocity/ directory or as a parameter. A user defined configset could contain renderable, potentially malicious, templates. Parameter provided templates are disabled by default, but can be enabled by setting params.resource.loader.enabled by defining a response writer with that setting set to true. Defining a response writer requires configuration API access. Solr 8.4 removed the params resource loader entirely, and only enables the configset-provided template rendering when the configset is trusted (has been uploaded by an authenticated user).

CVSS v3
7.5
EG Score
9.0CRITICALhigh confidence
EG Risk
74
EG Risk 74/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (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, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
99%
EPSS %ILE
99th
KEV
⚠ Exploited

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.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is the CISA KEV floor for confirmed exploitation, not an impact rating: its impact severity (EG Severity) is CVSS 7.5 HIGH.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
99% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 14 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, Attend at medium and Act at high mission impact.

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

Exploitation active (CISA Vulnrichment) · Automatable no (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 & forensic triage if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable no (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

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://nvd.nist.gov/vuln/detail/CVE-2019-17558

Published

December 30, 2019

Last Modified

October 27, 2025

Vendor Advisories for CVE-2019-17558(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.apache.solr:solr-core @ 8.4.0 (fixes >= 8.0.0, <= 8.3.1)—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
lucene-solr3.6.2+dfsg-24, 3.6.2+dfsg-25, 3.6.2+dfsg-26, 3.6.2+dfsg-27
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr3.6.2+dfsg-26, 3.6.2+dfsg-27
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr3.6.2+dfsg-26, 3.6.2+dfsg-27
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr3.6.2+dfsg-26, 3.6.2+dfsg-27
  • every version on: no fix on record
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.solr:solr-core8.0.0 ... 8.3.1 (6 versions)
  • 5.0.0 up to 8.4.0: fixed in 8.4.0
  • 6.0.0 up to 8.4.0: fixed in 8.4.0
  • 7.0.0 up to 8.4.0: fixed in 8.4.0
  • 8.0.0 up to 8.4.0: fixed in 8.4.0
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 22× 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 159 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 59 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(6 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 2 Exploit-DB entries, 2 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-48338✓ verified
    Published Apr 16, 2020

    Apache Solr - Remote Code Execution via Velocity Template (Metasploit)

    Open source ↗
  • Metasploitexploit/multi/http/solr_velocity_rce✓ verified
    Published Apr 2, 2020

    Apache Solr Remote Code Execution via Velocity Template

    Open source ↗
  • Nucleihttp/cves/2019/CVE-2019-17558.yaml
    Published Sep 3, 2020

    Apache Solr <=8.3.1 - Remote Code Execution

    Open source ↗
  • GitHub PoCMa1Dong/Solr_CVE-2019-17558
    Published Aug 4, 2020

    Solr_CVE-2019-17558

    Open source ↗
  • GitHub PoCzhzyker/exphub
    Published Apr 1, 2020

    Exphub[漏洞利用脚本库] 包括Webloigc、Struts2、Tomcat、Nexus、Solr、Jboss、Drupal的漏洞利用脚本,最新添加CVE-2020-14882、CVE-2020-11444、CVE-2020-10204、CVE-2020-10199、CVE-2020-1938、CVE-2020-2551、CVE-2020-2555、CVE-2020-2883、CVE-2019-17558、CVE-2019-6340

    Open source ↗
  • Exploit-DBEDB-47572
    Published Nov 1, 2019

    Apache Solr 8.2.0 - Remote Code Execution

    Open source ↗

Frequently asked(6)

What is CVE-2019-17558?
CVE-2019-17558 is a critical-severity vulnerability; its CVE record was published on December 30, 2019. Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter. A Velocity template can be provided through Velocity templates in a configset velocity/ directory or as a parameter. A user defined configset could contain renderable, potentially…
When was the CVE record for CVE-2019-17558 published?
The CVE record for CVE-2019-17558 was published on December 30, 2019. 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 27, 2025; the record at its source may have been updated since.
Is CVE-2019-17558 actively exploited?
Yes. CISA added CVE-2019-17558 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Apache Solr. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2019-17558?
CVE-2019-17558 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2019-17558?
CVE-2019-17558 affects Apache Solr. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2019-17558?
A fix for CVE-2019-17558 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-17558 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-17558

Explore →

Is Your Infrastructure Affected by CVE-2019-17558?

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