Skip to content
Vulnerability Intelligence

CVE-2023-50386

HighExploitedPublic exploit

Apache Solr: Backup/Restore APIs allow for deployment of executables in malicious ConfigSets

Published Feb 9, 2024 · Updated Oct 8, 2026 · Also known as BIT-solr-2023-50386, DEBIAN-CVE-2023-50386, GHSA-37vr-vmg4-jwpw, UBUNTU-CVE-2023-50386

Key Facts

Patch immediately
  • CVE-2023-50386 is a high-severity vulnerability (CVSS 8.8 v3.1) affecting Solr (Apache), lucene-solr (debian), org.apache.solr:solr-core (maven).
  • It is exploited in the wild, listed in Industry KEV feed since Sep 18, 2024. Public exploit code is available.
  • EPSS estimates a 84% probability of exploitation in the next 30 days.
  • Fixed versions are available, including Solr 8.11.3, Solr 9.4.1, Solr 9.5.0-r0.
  • Brandefense priority: patch immediately, because it is listed as exploited in the wild.

CVSS v3.1

8.8

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS (30-day exploit likelihood)

84%

Higher than 99.6% of all scored CVEs

Exploited in the wild

Yes

1 catalog listing

Public exploit code

Available

Proof-of-concept or weaponized module

Get the full CVE-2023-50386 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

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.

Known-Exploited Catalog Listings

CatalogAddedRemediation dueRansomware use
Industry KEV feedSep 18, 2024n/aNot reported

Required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Affected Products

17 affected entries in total
ProductAffected versionsFixed in
SolrApache>= 6.0.08.11.3
lucene-solrdebianSee advisory3.6.2+dfsg-23
org.apache.solr:solr-coremaven>= 6.0.08.11.3

Patched Releases

Solr

8.11.3, 9.4.1, 9.5.0-r0

lucene-solr

3.6.2+dfsg-23

org.apache.solr:solr-core

8.11.3, 9.4.1

Timeline

  1. Publicly disclosed

    Feb 9, 2024

  2. Added to Industry KEV feed

    Sep 18, 2024

  3. Last updated

    Oct 8, 2026

Weakness Type

  • CWE-434 Unrestricted Upload of File with Dangerous Type
  • CWE-913 Improper Control of Dynamically-Managed Code Resources

References

11 more references in the full CVE brief

FAQ

Common Questions.

Is CVE-2023-50386 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.

Request A Demo