CVE-2019-0193

HIGHNVD 7.29.0
EchelonGraph scoreHIGH confidence

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.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
7.2
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 84%CVSS: 7.2Exploit: NoneExposed: 0

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.0(high)
EPSS
99.7%
KEV
⚠ Exploited

Published

August 1, 2019

Last Modified

October 27, 2025

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntusolr-tomcat (3.6.2+dfsg-8ubuntu0.1+esm1) @ xenial2026-07-11ubuntu

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)
PackageVulnerable rangeFixed inDependents
org.apache.solr:solr-core1.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.

  1. 2026-07-11 20:39 UTCEG score recompute
  2. 2026-07-11 20:39 UTCVendor advisory
  3. 2026-07-11 16:43 UTCEG score recompute
  4. 2026-07-11 16:43 UTCVendor advisory
  5. 2026-07-11 12:47 UTCEG score recompute
  6. 2026-07-11 12:47 UTCVendor advisory
  7. 2026-07-11 08:51 UTCEG score recompute
  8. 2026-07-11 08:51 UTCVendor advisory
  9. 2026-07-11 04:54 UTCEG score recompute
  10. 2026-07-11 04:54 UTCVendor advisory
  11. 2026-07-11 00:58 UTCEG score recompute
  12. 2026-07-11 00:58 UTCVendor advisory
  13. 2026-07-10 21:03 UTCEG score recompute
  14. 2026-07-10 21:03 UTCVendor advisory
  15. 2026-07-10 17:52 UTCCISA KEV update
  16. 2026-07-10 17:06 UTCEG score recompute
  17. 2026-07-10 13:09 UTCEG score recompute
  18. 2026-07-10 13:09 UTCVendor advisory
  19. 2026-07-10 09:13 UTCEG score recompute
  20. 2026-07-10 09:13 UTCVendor advisory
  21. 2026-07-10 05:17 UTCEG score recompute
  22. 2026-07-10 05:17 UTCVendor advisory
  23. 2026-07-10 01:17 UTCEG score recompute
  24. 2026-07-10 01:17 UTCVendor advisory
  25. 2026-07-09 21:20 UTCEG score recompute
Show 75 more
  1. 2026-07-09 21:20 UTCVendor advisory
  2. 2026-07-09 19:06 UTCEPSS rescore
  3. 2026-07-09 17:24 UTCEG score recompute
  4. 2026-07-09 13:29 UTCEG score recompute
  5. 2026-07-09 09:33 UTCEG score recompute
  6. 2026-07-09 05:37 UTCEG score recompute
  7. 2026-07-09 01:39 UTCEG score recompute
  8. 2026-07-08 21:41 UTCEG score recompute
  9. 2026-07-08 21:41 UTCVendor advisory
  10. 2026-07-08 17:45 UTCEG score recompute
  11. 2026-07-08 13:50 UTCEG score recompute
  12. 2026-07-08 09:54 UTCEG score recompute
  13. 2026-07-08 09:54 UTCVendor advisory
  14. 2026-07-08 05:58 UTCEG score recompute
  15. 2026-07-08 05:58 UTCVendor advisory
  16. 2026-07-08 02:03 UTCEG score recompute
  17. 2026-07-08 02:03 UTCVendor advisory
  18. 2026-07-07 22:07 UTCEG score recompute
  19. 2026-07-07 19:01 UTCCISA KEV update
  20. 2026-07-07 18:10 UTCEG score recompute
  21. 2026-07-07 17:16 UTCCISA KEV update
  22. 2026-07-07 14:13 UTCEG score recompute
  23. 2026-07-07 14:13 UTCVendor advisory
  24. 2026-07-07 10:16 UTCEG score recompute
  25. 2026-07-07 06:20 UTCEG score recompute
  26. 2026-07-07 02:25 UTCEG score recompute
  27. 2026-07-06 22:27 UTCEG score recompute
  28. 2026-07-06 22:27 UTCVendor advisory
  29. 2026-07-06 18:31 UTCEG score recompute
  30. 2026-07-06 16:25 UTCEPSS rescore
  31. 2026-07-06 16:24 UTCEPSS rescore
  32. 2026-07-06 14:36 UTCEG score recompute
  33. 2026-07-06 10:38 UTCEG score recompute
  34. 2026-07-06 10:38 UTCVendor advisory
  35. 2026-07-06 06:37 UTCEG score recompute
  36. 2026-07-06 06:37 UTCVendor advisory
  37. 2026-07-06 02:42 UTCEG score recompute
  38. 2026-07-06 02:42 UTCVendor advisory
  39. 2026-07-06 02:20 UTCEPSS rescore
  40. 2026-07-05 22:46 UTCEG score recompute
  41. 2026-07-05 18:49 UTCEG score recompute
  42. 2026-07-05 18:49 UTCVendor advisory
  43. 2026-07-05 14:53 UTCEG score recompute
  44. 2026-07-05 10:57 UTCEG score recompute
  45. 2026-07-05 10:57 UTCVendor advisory
  46. 2026-07-05 07:01 UTCEG score recompute
  47. 2026-07-05 03:04 UTCEG score recompute
  48. 2026-07-05 03:04 UTCVendor advisory
  49. 2026-07-05 02:27 UTCEPSS rescore
  50. 2026-07-04 23:07 UTCEG score recompute
  51. 2026-07-04 23:07 UTCVendor advisory
  52. 2026-07-04 19:12 UTCEG score recompute
  53. 2026-07-04 19:12 UTCVendor advisory
  54. 2026-07-04 15:16 UTCEG score recompute
  55. 2026-07-04 11:19 UTCEG score recompute
  56. 2026-07-04 11:19 UTCVendor advisory
  57. 2026-07-04 07:23 UTCEG score recompute
  58. 2026-07-04 03:27 UTCEG score recompute
  59. 2026-07-04 03:27 UTCVendor advisory
  60. 2026-07-03 23:30 UTCEG score recompute
  61. 2026-07-03 23:30 UTCVendor advisory
  62. 2026-07-03 19:34 UTCEG score recompute
  63. 2026-07-03 19:34 UTCVendor advisory
  64. 2026-07-03 15:38 UTCEG score recompute
  65. 2026-07-03 15:38 UTCVendor advisory
  66. 2026-07-03 11:43 UTCEG score recompute
  67. 2026-07-03 07:46 UTCEG score recompute
  68. 2026-07-03 03:49 UTCEG score recompute
  69. 2026-07-02 23:54 UTCEG score recompute
  70. 2026-07-02 23:54 UTCVendor advisory
  71. 2026-07-02 19:58 UTCEG score recompute
  72. 2026-07-02 19:58 UTCVendor advisory
  73. 2026-07-02 16:03 UTCEG score recompute
  74. 2026-07-02 16:03 UTCVendor advisory
  75. 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_exploit
    First seen Aug 12, 2019

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

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

    Apache Solr DataImport Handler RCE

    Open source ↗
  • GitHub PoCxConsoIe/CVE-2019-0193
    First seen Mar 18, 2019
    Open source ↗
  • Nucleihttp/cves/2019/CVE-2019-0193.yaml
    First seen Jan 1, 2019

    Apache Solr DataImportHandler <8.2.0 - Remote Code Execution

    Open source ↗

Frequently asked(6)

What is CVE-2019-0193?
CVE-2019-0193 is a high vulnerability 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 disclosed?
CVE-2019-0193 was first published in the National Vulnerability Database on August 1, 2019, with the most recent update on October 27, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 patching attention.
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.
Which products are affected by CVE-2019-0193?
CVE-2019-0193 affects Apache Solr. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2019-0193?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-0193, 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-0193

Explore →

Is Your Infrastructure Affected by CVE-2019-0193?

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