CVE-2023-50386

HIGHNVD 8.89.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 87% probability of exploitation within the next 30 days (top 0.6% of all CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Weaponized
8.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 84%
CISA-KEV: Not listedEPSS: 84%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Improper Control of Dynamically-Managed Code Resources, Unrestricted Upload of File with Dangerous Type, Inclusion of Functionality from Untrusted Control Sphere vulnerability in Apache Solr.This issue affects Apache Solr: from 6.0.0 through 8.11.2, from 9.0.0 before 9.4.1.

In the affected versions, Solr ConfigSets accepted Java jar and class files to be uploaded through the ConfigSets API. When backing up Solr Collections, these configSet files would be saved to disk when using the LocalFileSystemRepository (the default for backups). If the backup was saved to a directory that Solr uses in its ClassPath/ClassLoaders, then the jar and class files would be available to use with any ConfigSet, trusted or untrusted.

When Solr is run in a secure way (Authorization enabled), as is strongly suggested, this vulnerability is limited to extending the Backup permissions with the ability to add libraries. Users are recommended to upgrade to version 8.11.3 or 9.4.1, which fix the issue. In these versions, the following protections have been added:

* Users are no longer able to upload files to a configSet that could be executed via a Java ClassLoader. * The Backup API restricts saving backups to directories that are used in the ClassLoader.

CVSS v3
8.8
EG Score
9.0(high)
EPSS
99.7%
KEV
Not listed

Published

February 9, 2024

Last Modified

April 24, 2025

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.solr:solr-core9.0.0 ... 9.4.0 (7 versions)9.4.1

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 2× in last 7d / 22× 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.

  1. 2026-07-11 08:26 UTCEPSS rescore
  2. 2026-07-08 15:13 UTCEPSS rescore
  3. 2026-07-04 06:29 UTCEPSS rescore
  4. 2026-07-04 06:29 UTCEPSS rescore
  5. 2026-07-01 15:05 UTCEPSS rescore
  6. 2026-06-29 14:05 UTCEPSS rescore
  7. 2026-06-28 14:06 UTCEPSS rescore
  8. 2026-06-28 14:06 UTCEPSS rescore
  9. 2026-06-27 03:07 UTCEPSS rescore
  10. 2026-06-26 21:07 UTCOSV refresh
  11. 2026-06-24 14:04 UTCEPSS rescore
  12. 2026-06-24 14:04 UTCEPSS rescore
  13. 2026-06-23 21:31 UTCEPSS rescore
  14. 2026-06-23 21:31 UTCEPSS rescore
  15. 2026-06-21 01:58 UTCEPSS rescore
  16. 2026-06-21 01:58 UTCEPSS rescore
  17. 2026-06-17 17:51 UTCEPSS rescore
  18. 2026-06-15 17:47 UTCEPSS rescore
  19. 2026-06-13 22:59 UTCEPSS rescore
  20. 2026-06-13 22:59 UTCEPSS rescore
  21. 2026-06-12 23:11 UTCEPSS rescore
  22. 2026-06-12 23:10 UTCEPSS rescore
  23. 2026-06-11 13:59 UTCEPSS rescore
  24. 2026-06-10 22:17 UTCEPSS rescore
  25. 2026-06-09 07:30 UTCOSV refresh
Show 22 more
  1. 2026-06-05 22:46 UTCEPSS rescore
  2. 2026-06-05 22:46 UTCEPSS rescore
  3. 2026-06-05 06:09 UTCEPSS rescore
  4. 2026-06-05 06:09 UTCEPSS rescore
  5. 2026-06-05 06:09 UTCEPSS rescore
  6. 2026-06-04 13:11 UTCEPSS rescore
  7. 2026-06-04 13:11 UTCEPSS rescore
  8. 2026-06-04 13:11 UTCEPSS rescore
  9. 2026-06-02 20:12 UTCEPSS rescore
  10. 2026-06-02 20:12 UTCEPSS rescore
  11. 2026-06-01 13:51 UTCEPSS rescore
  12. 2026-06-01 13:51 UTCEPSS rescore
  13. 2026-05-31 22:30 UTCEPSS rescore
  14. 2026-05-31 22:30 UTCEPSS rescore
  15. 2026-05-29 13:43 UTCEPSS rescore
  16. 2026-05-28 13:44 UTCEPSS rescore
  17. 2026-05-27 13:39 UTCEPSS rescore
  18. 2026-05-27 13:39 UTCEPSS rescore
  19. 2026-05-26 07:18 UTCEPSS rescore
  20. 2026-05-26 07:18 UTCEPSS rescore
  21. 2026-05-26 07:18 UTCEPSS rescore
  22. 2026-05-24 08:51 UTCEG score recompute

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCvvmdx/Apache-Solr-RCE_CVE-2023-50386_POC
    First seen Feb 29, 2024

    Apache Solr Backup/Restore APIs RCE Poc (CVE-2023-50386)

    Open source ↗
  • Metasploitexploit/linux/http/apache_solr_backup_restore✓ verified
    First seen Feb 24, 2024

    Apache Solr Backup/Restore APIs RCE

    Open source ↗

Frequently asked(5)

What is CVE-2023-50386?
CVE-2023-50386 is a high vulnerability published on February 9, 2024. Improper Control of Dynamically-Managed Code Resources, Unrestricted Upload of File with Dangerous Type, Inclusion of Functionality from Untrusted Control Sphere vulnerability in Apache Solr.This issue affects Apache Solr: from 6.0.0 through 8.11.2, from 9.0.0 before 9.4.1. In the affected…
When was CVE-2023-50386 disclosed?
CVE-2023-50386 was first published in the National Vulnerability Database on February 9, 2024, with the most recent update on April 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-50386 actively exploited?
CVE-2023-50386 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-50386?
CVE-2023-50386 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2023-50386?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-50386, 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-2023-50386

Explore →

Is Your Infrastructure Affected by CVE-2023-50386?

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