Solr 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
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 March 3, 2026
EOL

F5 Networks Solr 9 became EOL in 2026.

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 1 vulnerability in F5 Networks Solr with an average score of 7.1 out of ten.

Year Vulnerabilities Average Score
2026 1 7.10

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

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.

F5 Networks
Vendor

subscribe