CVE-2026-22022
BaseFortify
Publication date: 2026-01-21
Last updated on: 2026-01-27
Assigner: Apache Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apache | solr | From 5.3.0 (inc) to 9.10.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-285 | The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects Apache Solr versions 5.3.0 through 9.10.0 when using the RuleBasedAuthorizationPlugin with certain configurations. It allows unauthorized access to specific Solr APIs due to insufficient input validation. The vulnerability only applies if the plugin configuration specifies multiple roles, uses certain predefined permission rules (config-read, config-edit, schema-read, metrics-read, or security-read), does not define the 'all' permission, and if the network setup allows unfiltered client requests to Solr.
How can this vulnerability impact me? :
This vulnerability can allow unauthorized users to access certain Solr APIs that they should not have permission to use. This could lead to exposure or modification of configuration, schema, metrics, or security-related information within Solr, potentially compromising the integrity and confidentiality of the system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection involves verifying if your Apache Solr deployment uses the RuleBasedAuthorizationPlugin with multiple roles and specific permission rules as described. You should check your security.json configuration for the presence of multiple roles, use of permissions like "config-read", "config-edit", "schema-read", "metrics-read", or "security-read", and absence of the "all" permission. Additionally, verify if your network setup allows unfiltered HTTP/HTTPS requests to Solr. Specific commands are not provided in the available resources.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating your RuleBasedAuthorizationPlugin configuration to specify the "all" pre-defined permission and associating it with an "admin" or other privileged role. Alternatively, upgrade your Apache Solr deployment to version 9.10.1 or later, which is outside the impacted range.