F5 Networks Solr
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in F5 Networks Solr.
Recent F5 Networks Solr Security Advisories
| Advisory | Title | Published |
|---|---|---|
| K000160725 | K000160725: Apache Solr vulnerability CVE-2026-22022 | April 13, 2026 |
| K000160272 | K000160272: Apache Solr vulnerability CVE-2026-22444 | March 9, 2026 |
| K50133242 | Apache Solr vulnerability CVE-2019-17558 | July 23, 2021 |
EOL Dates
Ensure that you are using a supported version of F5 Networks Solr. Here are some end of life, and end of support dates for F5 Networks Solr.
| Release | EOL Date | Status |
|---|---|---|
| 10 | - |
Active
|
| 9 | - |
Active
|
| 8 | October 25, 2024 |
EOL
F5 Networks Solr 8 became EOL in 2024. |
| 7 | May 11, 2022 |
EOL
F5 Networks Solr 7 became EOL in 2022. |
| 6 | March 13, 2019 |
EOL
F5 Networks Solr 6 became EOL in 2019. |
| 5 | October 24, 2017 |
EOL
F5 Networks Solr 5 became EOL in 2017. |
| 4 | - |
Active
|
| 3 | - |
Active
|
| 1 | - |
Active
|
By the Year
In 2026 there have been 2 vulnerabilities in F5 Networks Solr with an average score of 7.7 out of ten.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 2 | 7.65 |
It may take a day or so for new Solr vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent F5 Networks Solr Security Vulnerabilities
VULN: Apache Solr 5.3.09.10.0 RuleBasedAuthorizationPlugin unauthorized API access
CVE-2026-22022
8.2 - High
- January 21, 2026
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.
AuthZ
Apache Solr 8.6-9.10.0 Core-Create API Path Validation Bypass
CVE-2026-22444
7.1 - High
- January 21, 2026
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.
Improper Input Validation
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for F5 Networks Solr or by F5 Networks? Click the Watch button to subscribe.
