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.0CRITICALhigh confidence
- EG Risk
- 81EG Risk 81/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%CISA SSVC: Track at low, Attend at medium and Act at high mission impact.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
CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
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 | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | solr-tomcat (3.6.2+dfsg-18~18.04.1~esm2) @ bionic | 2026-10-09 | 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
(7 across 7 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| lucene-solr | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| lucene-solr | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| lucene-solr | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| lucene-solr | — |
| — |
Debian:8(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| lucene-solr | 3.6.2+dfsg-5, 3.6.2+dfsg-5+deb8u1, 3.6.2+dfsg-5+deb8u2 |
| — |
Debian:9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| lucene-solr | 3.6.2+dfsg-10, 3.6.2+dfsg-10+deb9u1, 3.6.2+dfsg-10+deb9u2 |
| — |
Maven(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| org.apache.solr:solr-core | 1.3.0 ... 8.1.1 (86 versions) |
| — |
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 38× in last 7d / 193× 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 758 total refreshes for this CVE.
- 2026-10-09 21:33 UTCVendor advisory
- 2026-10-09 17:37 UTCVendor advisory
- 2026-10-09 13:40 UTCVendor advisory
- 2026-10-09 09:44 UTCVendor advisory
- 2026-10-09 05:48 UTCVendor advisory
- 2026-10-08 21:57 UTCVendor advisory
- 2026-10-08 10:05 UTCVendor advisory
- 2026-10-08 06:10 UTCVendor advisory
- 2026-10-08 02:14 UTCEG score recompute
- 2026-10-07 23:42 UTCEPSS rescore
- 2026-10-07 22:17 UTCVendor advisory
- 2026-10-07 18:21 UTCVendor advisory
- 2026-10-07 10:30 UTCVendor advisory
- 2026-10-07 06:34 UTCVendor advisory
- 2026-10-07 02:39 UTCVendor advisory
- 2026-10-06 22:43 UTCVendor advisory
- 2026-10-06 18:47 UTCVendor advisory
- 2026-10-06 14:52 UTCVendor advisory
- 2026-10-06 10:56 UTCVendor advisory
- 2026-10-06 07:01 UTCVendor advisory
- 2026-10-06 03:05 UTCVendor advisory
- 2026-10-05 23:09 UTCVendor advisory
- 2026-10-05 19:13 UTCVendor advisory
- 2026-10-05 11:18 UTCVendor advisory
- 2026-10-05 07:23 UTCVendor advisory
Show 75 moreShow fewer
- 2026-10-05 03:27 UTCVendor advisory
- 2026-10-04 23:32 UTCVendor advisory
- 2026-10-04 19:36 UTCVendor advisory
- 2026-10-04 15:41 UTCVendor advisory
- 2026-10-04 11:45 UTCVendor advisory
- 2026-10-04 07:50 UTCVendor advisory
- 2026-10-03 23:56 UTCVendor advisory
- 2026-10-03 20:00 UTCVendor advisory
- 2026-10-03 16:05 UTCEG score recompute
- 2026-10-03 16:05 UTCVendor advisory
- 2026-10-03 14:21 UTCEPSS rescore
- 2026-10-03 12:10 UTCVendor advisory
- 2026-10-03 08:14 UTCVendor advisory
- 2026-10-03 04:17 UTCVendor advisory
- 2026-10-03 00:21 UTCVendor advisory
- 2026-10-02 16:27 UTCVendor advisory
- 2026-10-02 12:32 UTCVendor advisory
- 2026-10-02 08:36 UTCVendor advisory
- 2026-10-02 04:41 UTCVendor advisory
- 2026-10-01 20:49 UTCEG score recompute
- 2026-10-01 19:44 UTCEPSS rescore
- 2026-10-01 12:54 UTCVendor advisory
- 2026-10-01 08:58 UTCVendor advisory
- 2026-10-01 05:02 UTCVendor advisory
- 2026-10-01 01:07 UTCVendor advisory
- 2026-09-30 21:11 UTCVendor advisory
- 2026-09-30 17:16 UTCVendor advisory
- 2026-09-30 13:21 UTCVendor advisory
- 2026-09-30 05:26 UTCVendor advisory
- 2026-09-30 01:30 UTCVendor advisory
- 2026-09-29 13:38 UTCVendor advisory
- 2026-09-29 09:41 UTCVendor advisory
- 2026-09-29 05:44 UTCVendor advisory
- 2026-09-29 01:49 UTCVendor advisory
- 2026-09-28 21:53 UTCEG score recompute
- 2026-09-28 21:53 UTCVendor advisory
- 2026-09-28 13:59 UTCVendor advisory
- 2026-09-28 10:03 UTCVendor advisory
- 2026-09-28 06:05 UTCVendor advisory
- 2026-09-28 02:10 UTCVendor advisory
- 2026-09-27 22:15 UTCVendor advisory
- 2026-09-27 21:51 UTCCISA KEV update
- 2026-09-27 18:20 UTCVendor advisory
- 2026-09-27 14:24 UTCVendor advisory
- 2026-09-27 10:29 UTCVendor advisory
- 2026-09-27 06:33 UTCVendor advisory
- 2026-09-27 02:37 UTCVendor advisory
- 2026-09-26 22:41 UTCVendor advisory
- 2026-09-26 18:46 UTCVendor advisory
- 2026-09-26 14:51 UTCVendor advisory
- 2026-09-26 06:57 UTCVendor advisory
- 2026-09-25 23:06 UTCVendor advisory
- 2026-09-25 19:35 UTCCISA KEV update
- 2026-09-25 14:55 UTCCISA KEV update
- 2026-09-25 11:16 UTCVendor advisory
- 2026-09-25 07:20 UTCVendor advisory
- 2026-09-25 03:24 UTCVendor advisory
- 2026-09-24 23:29 UTCVendor advisory
- 2026-09-24 19:33 UTCVendor advisory
- 2026-09-24 19:31 UTCCISA KEV update
- 2026-09-24 15:37 UTCEG score recompute
- 2026-09-24 15:37 UTCVendor advisory
- 2026-09-24 13:59 UTCEPSS rescore
- 2026-09-24 11:42 UTCVendor advisory
- 2026-09-24 07:46 UTCVendor advisory
- 2026-09-24 03:50 UTCVendor advisory
- 2026-09-23 23:51 UTCVendor advisory
- 2026-09-23 19:56 UTCVendor advisory
- 2026-09-23 16:00 UTCVendor advisory
- 2026-09-23 12:05 UTCVendor advisory
- 2026-09-23 08:09 UTCVendor advisory
- 2026-09-23 04:14 UTCVendor advisory
- 2026-09-23 00:18 UTCVendor advisory
- 2026-09-22 20:23 UTCVendor advisory
- 2026-09-22 19:36 UTCCISA KEV update
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 product + same CWE)
Same product
10 shownDebian:8:lucene-solr · Debian:11:lucene-solr
- CVE-2017-12629EG 9.8EPSS p100CRITICAL
- CVE-2018-1308EG 7.5EPSS p97HIGH
- CVE-2017-3163EG 7.5EPSS p94HIGH
- CVE-2023-50386NVD 8.8EG 9.0EPSS p100CRITICAL
- CVE-2019-17558NVD 7.5EG 9.0 KEVEPSS p100CRITICAL
- CVE-2023-50292EG 7.5HIGH
- CVE-2023-50291EG 7.5HIGH
- CVE-2017-3164EG 7.5EPSS p97HIGH
- CVE-2012-6612EG 7.5EPSS p96HIGH
- CVE-2013-6408EG 6.4EPSS p96MEDIUM
Same CWE
10 shownCWE-94
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.