Distributed search in Apache Solr lets one request ask a server to query other indexes and merge the results. Without the right controls the same feature can be used to read an index the caller has no credentials for. Opensolr does not allow it.
01 · At a glance
shards parameter in Apache Solr 1.3 to 7.6.02 · What it is
A query can carry a shards parameter with a list of addresses. Solr then sends the query to each of those addresses itself and merges the answers.
Those follow-up requests start from the Solr server, not from the user. If access rules are applied only to the request the user sent, the follow-up requests can reach places the user could not reach directly. Apache Solr 7.7 added an allow list for this parameter as the fix for CVE-2017-3164.
03 · Who is affected
- Solr servers that hold indexes for more than one party, each with its own credentials.
- Servers that run a Solr older than 7.7, or that pass every query parameter through to Solr untouched.
04 · How to protect a Solr server
- Keep the Solr allow list for shard addresses on, and list only the hosts that really are shards of your own cluster.
- Drop distributed search parameters from requests that come from users, unless distributed search is part of the service you offer.
- Apply access rules to the requests Solr makes on a user's behalf, not only to the first one.
- Keep Solr behind authentication and never expose it directly to the internet.
<!-- solr.xml: only these hosts may be named in shards --> <solr> <str name="allowUrls">${solr.allowUrls:solr1.internal:8983,solr2.internal:8983}</str> </solr>
05 · Opensolr and this vulnerability
Status on November 20, 2026. On Opensolr, a request made on one Opensolr Index cannot read an index that belongs to another account. The control is enforced platform-wide and has been verified on every server. Nothing is required from you.
- Opensolr watches newly published vulnerabilities for every component of the platform, around the clock.
- Each advisory is assessed against the platform as soon as it is published.
- The fix is applied, or the vulnerable condition is closed, and the result is verified before the case is closed.
More on how Opensolr protects your data: Opensolr Trust Center and all security pages. Questions about a vulnerability that is not listed: contact Opensolr.
Background: CVE-2017-3164 at NVD · Apache Solr security page.