CVE-2026-22022VulnerabilityPublished 21 Jan 2026

CVE-2026-22022: Apache Solr · Improper Authorization

Affects Apache SolrSource CVE Database V5

Not known to be exploited · CVSS 8.2 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Solr	Affected >=5.3 <=9.10.0	Fixed in–
Mavenorg.apache.solr/solr-core`pkg:maven/org.apache.solr/solr-core`Other threats	Affected =5.3.0 <=9.10.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-22022, European organizations should: 1) Immediately upgrade Apache Solr to version 9.10.1 or later, where the vulnerability is fixed. 2) Review and audit RuleBasedAuthorizationPlugin configurations to ensure the 'all' predefined permission is included and assigned exclusively to admin or highly privileged roles, thereby enforcing strict access control. 3) Implement network-level protections such as firewalls, reverse proxies, or API gateways to restrict direct, unfiltered access to Solr endpoints, limiting exposure to trusted internal networks or authenticated clients only. 4) Employ monitoring and logging of Solr API access to detect anomalous or unauthorized requests promptly. 5) Conduct penetration testing and security assessments focused on Solr deployments to verify the effectiveness of authorization controls. 6) Educate DevOps and security teams about the risks of misconfigured authorization plugins and the importance of least privilege principles in Solr security configurations. These steps go beyond generic advice by focusing on configuration hardening, network segmentation, and proactive detection tailored to this specific vulnerability.

Description

Deployments of Apache Solr 5.3.0 through 9.10.0 that rely on Solr's "Rule Based Authorization Plugin" are vulnerable to allowing unauthorized access to certain Solr APIs, due to insufficiently strict input validation in those components. Only deployments that meet all of the following criteria are impacted by this vulnerability: * Use of Solr's "RuleBasedAuthorizationPlugin" * A RuleBasedAuthorizationPlugin config (see security.json) that specifies multiple "roles" * A RuleBasedAuthorizationPlugin permission list (see security.json) that uses one or more of the following pre-defined permission rules: "config-read", "config-edit", "schema-read", "metrics-read", or "security-read". * A RuleBasedAuthorizationPlugin permission list that doesn't define the "all" pre-defined permission * A networking setup that allows clients to make unfiltered network requests to Solr. (i.e. user-submitted HTTP/HTTPS requests reach Solr as-is, unmodified or restricted by any intervening proxy or gateway) Users can mitigate this vulnerability by ensuring that their RuleBasedAuthorizationPlugin configuration specifies the "all" pre-defined permission and associates the permission with an "admin" or other privileged role. Users can also upgrade to a Solr version outside of the impacted range, such as the recently released Solr 9.10.1.

Impact

For European organizations, this vulnerability poses a significant risk of unauthorized access to critical Solr APIs, potentially leading to exposure or unauthorized modification of search indexes, configurations, and security settings. This can compromise data confidentiality and integrity, disrupt search services, and undermine trust in data-driven applications. Organizations relying on Solr for enterprise search, e-commerce, or public sector data indexing could face operational disruptions or data breaches. The impact is heightened in sectors with strict data protection regulations such as GDPR, where unauthorized data access can lead to regulatory penalties and reputational damage. Since exploitation requires network access to Solr, organizations with publicly accessible Solr instances or insufficient network segmentation are particularly vulnerable. The absence of authentication requirements for exploitation increases the risk of automated or opportunistic attacks. Overall, the vulnerability threatens the confidentiality and integrity of data managed by Solr deployments across European enterprises and government agencies.

Summary

CVE-2026-22022 is a vulnerability classified under CWE-285 (Improper Authorization) affecting Apache Solr versions 5.3.0 through 9.10.0 when the RuleBasedAuthorizationPlugin is used with certain configurations. The vulnerability stems from insufficiently strict input validation within the plugin's authorization logic, which can allow unauthorized users to access specific Solr APIs that should be restricted. The conditions for exploitation include: (1) use of the RuleBasedAuthorizationPlugin, (2) a configuration specifying multiple roles, (3) permission lists that include predefined rules such as 'config-read', 'config-edit', 'schema-read', 'metrics-read', or 'security-read' but do not include the 'all' permission, and (4) network setups that allow direct, unfiltered HTTP/HTTPS requests to Solr instances. Under these conditions, an attacker can bypass intended access controls and perform unauthorized read or edit operations on Solr configurations, schemas, metrics, or security settings. This can lead to exposure or manipulation of sensitive data and system configurations. The vulnerability does not require user interaction or authentication but does require network access to the Solr service. No public exploits have been reported yet, but the risk remains significant due to the widespread use of Solr in enterprise search and data indexing. Mitigation is straightforward: upgrading to Solr 9.10.1 or later, or modifying the RuleBasedAuthorizationPlugin configuration to include the 'all' permission assigned to an admin or privileged role, effectively tightening access controls and preventing unauthorized API access.

CWE-285Improper Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that you perform access control checks related to your business logic. These checks may be different than the access control checks that you apply to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Cross Zone Scripting (opens in a new tab)
Directory Indexing (opens in a new tab)
Subverting Environment Variable Values (opens in a new tab)
Using Malicious Files (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 21 Jan 2026, 14:20 UTC

WeaknessesCWE-285

Technical details

References

Community reviews

Related threats