Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-22444

org.apache.solr/solr-core: Apache Solr: Insufficient file-access checking in standalone core-creation requests

Overview

Published
21 Jan 2026
Modified
17 Jun 2026
High CVE
2 Registry packages
1 OS packages
2 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

7.1 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

Weakness: CWE-20

Affected packages · 2

Packages affected by CVE-2026-22444
EcosystemPackageVulnerableFixed in
Bitnami solr >=8.6.0, <9.10.1 9.10.1
Maven org.apache.solr:solr-core >=8.6.0, <9.10.1 9.10.1

Open a package to see all its vulnerabilities.

Operating systems · 2 fixes

chainguard 1 release · 1 package

fixed 1
solr-9
chainguard fixes for CVE-2026-22444
ReleasePackageFixed in
solr-9 9.10.1-r1

minimos 1 release · 1 package

fixed 1
solr-9
minimos fixes for CVE-2026-22444
ReleasePackageFixed in
solr-9 9.10.1-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.