High

Apache Solr: Insufficient file-access checking in standalone core-creation requests

  • Disclosed: 21.01.2026
  • Updated: 11.10.2026 13:20

The "create core" API of Apache Solr 8.6 through 9.10.0 lacks sufficient input validation on some API parameters, which can cause Solr to check the existence of and attempt to read file-system paths that should be disallowed by Solr's "allowPaths" security setting https://https://solr.apache.org/guide/solr/latest/configuration-guide/configuring-solr-xml.html#the-solr-element .  These read-only accesses can allow users to create cores using unexpected configsets if any are accessible via the filesystem.  On Windows systems configured to allow UNC paths this can additionally cause disclosure of NTLM "user" hashes. 

Solr deployments are subject to this vulnerability if they meet the following criteria:

  • Solr is running in its "standalone" mode.
  • Solr's "allowPath" setting is being used to restrict file access to certain directories.
  • Solr's "create core" API is exposed and accessible to untrusted users.  This can happen if Solr's RuleBasedAuthorizationPlugin https://solr.apache.org/guide/solr/latest/deployment-guide/rule-based-authorization-plugin.html is disabled, or if it is enabled but the "core-admin-edit" predefined permission (or an equivalent custom permission) is given to low-trust (i.e. non-admin) user roles.

Users can mitigate this by enabling Solr's RuleBasedAuthorizationPlugin (if disabled) and configuring a permission-list that prevents untrusted users from creating new Solr cores.  Users should also upgrade to Apache Solr 9.10.1 or greater, which contain fixes for this issue.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Java / Kotlin (Maven) org.apache.solr:solr-core >= 8.6.0, < 9.10.1 9.10.1

References

CVSS score 7.1/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Weakness (CWE)
CWE-20
Platform
Java / Kotlin (Maven)
Package
org.apache.solr:solr-core
Disclosed
21.01.2026
Updated
11.10.2026 13:20

Sources and licenses

OSV / GitHub Advisory Database - GHSA-vc2w-4v3p-2mqw - CC BY 4.0

Vulnerability history: org.apache.solr:solr-core

All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (31) in the archive
Total entries
31
First → latest
10.2018 06.2026
Without a fix
1
Exploited in attacks
2

Severity breakdown

  • Critical 4
  • High 16
  • Medium 10
  • Low 1

Disclosures per year

  1. 2018: 5
  2. 2019: 3
  3. 2020: 2
  4. 2021: 1
  5. 2022: 11
  6. 2023: 0
  7. 2024: 4
  8. 2025: 2
  9. 2026: 3
Severity:
  1. High · 8.1 CVE-2026-44825 >= 9.4.0, <= 9.10.1, = 10.0.0 no fix
  2. Apache Solr: Insufficient file-access checking in standalone core-creation requests this entry
    High · 7.1 CVE-2026-22444 >= 8.6.0, < 9.10.1 9.10.1
  3. High · 8.8 CVE-2023-50386 >= 6.0.0, < 8.11.3, >= 9.0.0, < 9.4.1 8.11.3, 9.4.1
  4. High · 7.5 CVE-2023-50291 >= 6.0.0, < 8.11.3, >= 9.0.0, < 9.3.0 8.11.3, 9.3.0
  5. High · 7.5 CVE-2019-12401 < 5.0.0 5.0.0
  6. High · 7.5 CVE-2017-7660 >= 5.3.0, < 5.5.5, >= 6.0.0, < 6.6.0 5.5.5, 6.6.0
  7. High · 7.5 CVE-2017-9803 >= 6.2.0, < 6.6.1 6.6.1
  8. Critical · 9.8 CVE-2020-13957 >= 6.6.0, < 8.6.3 8.6.3
  9. High · 7.5 CVE-2021-29262 < 8.8.2 8.8.2
  10. High · 7.5 Exploited in attacks CVE-2019-17558 >= 5.0.0, < 8.4.0, >= 6.0.0, < 8.4.0, >= 7.0.0, < 8.4.0, >= 8.0.0, < 8.4.0 8.4.0
  11. Critical · 9.8 CVE-2019-12409 >= 8.1.1, < 8.3.0 8.3.0
  12. High · 7.2 Exploited in attacks CVE-2019-0193 < 8.2.0 8.2.0
  13. High · 7.5 CVE-2017-3164 >= 1.3.0, < 7.7.0 7.7.0
  14. Critical · 9.8 CVE-2019-0192 >= 5.0.0, < 7.0.0, >= 6.0.0, < 7.0.0 7.0.0
  15. High · 7.5 CVE-2017-3163 < 5.5.4, >= 6.0.0, < 6.4.1 5.5.4, 6.4.1
  16. Critical · 9.8 CVE-2017-12629 >= 7.0.0, < 7.1.0, >= 6.0.0, < 6.6.2, >= 5.5.0, < 5.5.5 7.1.0, 6.6.2, 5.5.5
  17. High · 7.5 CVE-2018-1308 >= 1.2, < 6.6.3, >= 7.0.0, < 7.3.0 6.6.3, 7.3.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.