CVE-2019-0193

CRITICALNVD 7.29.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-12-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.2 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.2 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-2019-0615 (ENISA EUVD) · GHSA-3gm7-v7vw-866c (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: 84%CVSS: 7.2Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

In Apache Solr, the DataImportHandler, an optional but popular module to pull in data from databases and other sources, has a feature in which the whole DIH configuration can come from a request's "dataConfig" parameter. The debug mode of the DIH admin screen uses this to allow convenient debugging / development of a DIH config. Since a DIH config can contain scripts, this parameter is a security risk. Starting with version 8.2.0 of Solr, use of this parameter requires setting the Java System property "enable.dih.dataConfigParam" to true.

CVSS v3
7.2
EG Score
9.0CRITICALhigh confidence
EG Risk
72
EG Risk 72/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)
Severity72% × 45%
Impact severity (EG Severity): CVSS 7.2 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
84%
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.2 HIGH.

EG Severity
7.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
84% 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-0193

Published

August 1, 2019

Last Modified

October 27, 2025

Vendor Advisories for CVE-2019-0193(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntusolr-tomcat (3.6.2+dfsg-8ubuntu0.1+esm1) @ xenial2026-11-03ubuntu
mavenorg.apache.solr:solr-core @ 8.2.0 (fixes < 8.2.0)—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

(7 across 7 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr—
  • every version up to 3.6.2+dfsg-22: fixed in 3.6.2+dfsg-22
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr—
  • every version up to 3.6.2+dfsg-22: fixed in 3.6.2+dfsg-22
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr—
  • every version up to 3.6.2+dfsg-22: fixed in 3.6.2+dfsg-22
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr—
  • every version up to 3.6.2+dfsg-22: fixed in 3.6.2+dfsg-22
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr3.6.2+dfsg-5, 3.6.2+dfsg-5+deb8u1, 3.6.2+dfsg-5+deb8u2
  • every version up to 3.6.2+dfsg-5+deb8u3: fixed in 3.6.2+dfsg-5+deb8u3
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
lucene-solr3.6.2+dfsg-10, 3.6.2+dfsg-10+deb9u1, 3.6.2+dfsg-10+deb9u2
  • every version up to 3.6.2+dfsg-10+deb9u3: fixed in 3.6.2+dfsg-10+deb9u3
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.solr:solr-core1.3.0 ... 8.1.1 (86 versions)
  • every version up to 8.2.0: fixed in 8.2.0
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Publicly available exploits

(4 references)

Public exploit code is referenced for this CVE (3 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.

  • Nucleihttp/cves/2019/CVE-2019-0193.yaml
    Published Aug 9, 2021

    Apache Solr DataImportHandler <8.2.0 - Remote Code Execution

    Open source ↗
  • GitHub PoC1135/solr_exploit
    Published Aug 12, 2019

    Apache Solr远程代码执行漏洞(CVE-2019-0193) Exploit

    Open source ↗
  • GitHub PoCjas502n/CVE-2019-0193
    Published Aug 9, 2019

    Apache Solr DataImport Handler RCE

    Open source ↗
  • GitHub PoCxConsoIe/CVE-2019-0193
    Published Mar 18, 2019
    Open source ↗

Frequently asked(6)

What is CVE-2019-0193?
CVE-2019-0193 is a critical-severity vulnerability; its CVE record was published on August 1, 2019. In Apache Solr, the DataImportHandler, an optional but popular module to pull in data from databases and other sources, has a feature in which the whole DIH configuration can come from a request's "dataConfig" parameter. The debug mode of the DIH admin screen uses this to allow convenient debugging…
When was CVE-2019-0193 made public?
CVE-2019-0193 was made public on July 31, 2019: that is the date its CVE record's CNA, Apache Software Foundation, gives for when the vulnerability was made public. The CVE record itself was published on August 1, 2019. 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-0193 actively exploited?
Yes. CISA added CVE-2019-0193 to the Known Exploited Vulnerabilities catalog on December 10, 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-0193?
CVE-2019-0193 has a CVSS v3 base score of 7.2 (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-0193?
CVE-2019-0193 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-0193?
A fix for CVE-2019-0193 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2019-0193 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-0193

Explore →

Is Your Infrastructure Affected by CVE-2019-0193?

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