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.
CVE-2019-0193
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. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 7.2
- EG Score
- 9.0(high)
- EPSS
- 99.7%
- KEV
- ⚠ Exploited
Published
August 1, 2019
Last Modified
October 27, 2025
Advisory Details (10)
Auto-updated Jun 11, 2026[SOLR-13669] [CVE-2019-0193] Remote Code Execution via DataImportHandler - ASF Jira
https://issues.apache.org/jira/browse/SOLR-13669Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | solr-tomcat (3.6.2+dfsg-8ubuntu0.1+esm1) @ xenial | 2026-07-11 | ubuntu |
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
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.apache.solr:solr-core | 1.3.0 ... 8.1.1 (86 versions) | 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 74× in last 7d / 329× 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.
Showing the most recent 100 of 485 total refreshes for this CVE.
- 2026-07-11 20:39 UTCEG score recompute
- 2026-07-11 20:39 UTCVendor advisory
- 2026-07-11 16:43 UTCEG score recompute
- 2026-07-11 16:43 UTCVendor advisory
- 2026-07-11 12:47 UTCEG score recompute
- 2026-07-11 12:47 UTCVendor advisory
- 2026-07-11 08:51 UTCEG score recompute
- 2026-07-11 08:51 UTCVendor advisory
- 2026-07-11 04:54 UTCEG score recompute
- 2026-07-11 04:54 UTCVendor advisory
- 2026-07-11 00:58 UTCEG score recompute
- 2026-07-11 00:58 UTCVendor advisory
- 2026-07-10 21:03 UTCEG score recompute
- 2026-07-10 21:03 UTCVendor advisory
- 2026-07-10 17:52 UTCCISA KEV update
- 2026-07-10 17:06 UTCEG score recompute
- 2026-07-10 13:09 UTCEG score recompute
- 2026-07-10 13:09 UTCVendor advisory
- 2026-07-10 09:13 UTCEG score recompute
- 2026-07-10 09:13 UTCVendor advisory
- 2026-07-10 05:17 UTCEG score recompute
- 2026-07-10 05:17 UTCVendor advisory
- 2026-07-10 01:17 UTCEG score recompute
- 2026-07-10 01:17 UTCVendor advisory
- 2026-07-09 21:20 UTCEG score recompute
Show 75 moreShow fewer
- 2026-07-09 21:20 UTCVendor advisory
- 2026-07-09 19:06 UTCEPSS rescore
- 2026-07-09 17:24 UTCEG score recompute
- 2026-07-09 13:29 UTCEG score recompute
- 2026-07-09 09:33 UTCEG score recompute
- 2026-07-09 05:37 UTCEG score recompute
- 2026-07-09 01:39 UTCEG score recompute
- 2026-07-08 21:41 UTCEG score recompute
- 2026-07-08 21:41 UTCVendor advisory
- 2026-07-08 17:45 UTCEG score recompute
- 2026-07-08 13:50 UTCEG score recompute
- 2026-07-08 09:54 UTCEG score recompute
- 2026-07-08 09:54 UTCVendor advisory
- 2026-07-08 05:58 UTCEG score recompute
- 2026-07-08 05:58 UTCVendor advisory
- 2026-07-08 02:03 UTCEG score recompute
- 2026-07-08 02:03 UTCVendor advisory
- 2026-07-07 22:07 UTCEG score recompute
- 2026-07-07 19:01 UTCCISA KEV update
- 2026-07-07 18:10 UTCEG score recompute
- 2026-07-07 17:16 UTCCISA KEV update
- 2026-07-07 14:13 UTCEG score recompute
- 2026-07-07 14:13 UTCVendor advisory
- 2026-07-07 10:16 UTCEG score recompute
- 2026-07-07 06:20 UTCEG score recompute
- 2026-07-07 02:25 UTCEG score recompute
- 2026-07-06 22:27 UTCEG score recompute
- 2026-07-06 22:27 UTCVendor advisory
- 2026-07-06 18:31 UTCEG score recompute
- 2026-07-06 16:25 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-06 14:36 UTCEG score recompute
- 2026-07-06 10:38 UTCEG score recompute
- 2026-07-06 10:38 UTCVendor advisory
- 2026-07-06 06:37 UTCEG score recompute
- 2026-07-06 06:37 UTCVendor advisory
- 2026-07-06 02:42 UTCEG score recompute
- 2026-07-06 02:42 UTCVendor advisory
- 2026-07-06 02:20 UTCEPSS rescore
- 2026-07-05 22:46 UTCEG score recompute
- 2026-07-05 18:49 UTCEG score recompute
- 2026-07-05 18:49 UTCVendor advisory
- 2026-07-05 14:53 UTCEG score recompute
- 2026-07-05 10:57 UTCEG score recompute
- 2026-07-05 10:57 UTCVendor advisory
- 2026-07-05 07:01 UTCEG score recompute
- 2026-07-05 03:04 UTCEG score recompute
- 2026-07-05 03:04 UTCVendor advisory
- 2026-07-05 02:27 UTCEPSS rescore
- 2026-07-04 23:07 UTCEG score recompute
- 2026-07-04 23:07 UTCVendor advisory
- 2026-07-04 19:12 UTCEG score recompute
- 2026-07-04 19:12 UTCVendor advisory
- 2026-07-04 15:16 UTCEG score recompute
- 2026-07-04 11:19 UTCEG score recompute
- 2026-07-04 11:19 UTCVendor advisory
- 2026-07-04 07:23 UTCEG score recompute
- 2026-07-04 03:27 UTCEG score recompute
- 2026-07-04 03:27 UTCVendor advisory
- 2026-07-03 23:30 UTCEG score recompute
- 2026-07-03 23:30 UTCVendor advisory
- 2026-07-03 19:34 UTCEG score recompute
- 2026-07-03 19:34 UTCVendor advisory
- 2026-07-03 15:38 UTCEG score recompute
- 2026-07-03 15:38 UTCVendor advisory
- 2026-07-03 11:43 UTCEG score recompute
- 2026-07-03 07:46 UTCEG score recompute
- 2026-07-03 03:49 UTCEG score recompute
- 2026-07-02 23:54 UTCEG score recompute
- 2026-07-02 23:54 UTCVendor advisory
- 2026-07-02 19:58 UTCEG score recompute
- 2026-07-02 19:58 UTCVendor advisory
- 2026-07-02 16:03 UTCEG score recompute
- 2026-07-02 16:03 UTCVendor advisory
- 2026-07-02 12:07 UTCEG score recompute
Publicly available exploits
(4 references)Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoC1135/solr_exploitFirst seen Aug 12, 2019
Apache Solr远程代码执行漏洞(CVE-2019-0193) Exploit
Open source ↗ - GitHub PoCjas502n/CVE-2019-0193First seen Aug 9, 2019
Apache Solr DataImport Handler RCE
Open source ↗ - Open source ↗GitHub PoCxConsoIe/CVE-2019-0193First seen Mar 18, 2019
- Nucleihttp/cves/2019/CVE-2019-0193.yamlFirst seen Jan 1, 2019
Apache Solr DataImportHandler <8.2.0 - Remote Code Execution
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu
Same CWE
10 shownCWE-94
- CVE-2006-1359NVD 0.0EG 9.0EPSS 99%NONE
- CVE-2005-1921NVD 0.0EG 9.0EPSS 100%NONE
- CVE-2005-3302EG 7.3HIGH
- CVE-2005-1876EG 4.5MEDIUM
- CVE-2003-1599EG 0.0NONE
- CVE-2006-1318EG 0.0EPSS 96%NONE
- CVE-2006-1301EG 0.0EPSS 95%NONE
- CVE-2006-1308EG 0.0EPSS 95%NONE
- CVE-2006-1309EG 0.0EPSS 95%NONE
- CVE-2006-1304EG 0.0EPSS 95%NONE
Frequently asked(6)
What is CVE-2019-0193?
When was CVE-2019-0193 disclosed?
Is CVE-2019-0193 actively exploited?
What is the CVSS score of CVE-2019-0193?
Which products are affected by CVE-2019-0193?
How do I remediate CVE-2019-0193?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-0193
Is Your Infrastructure Affected by CVE-2019-0193?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.