Incorrect Authorization in Apache Solr

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2018-11802: 2.02% estimated exploitation activity in the next 30 days; percentile 80.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

In Apache Solr, the cluster can be partitioned into multiple collections and only a subset of nodes actually host any given collection. However, if a node receives a request for a collection it does not host, it proxies the request to a relevant node and serves the request. Solr bypasses all authorization settings for such requests. This affects all Solr versions prior to 6.6.6 and 7.7 that use the default authorization mechanism of Solr (RuleBasedAuthorizationPlugin).

Published by the source

9 Feb 2022, 23:19 UTC

Last modified by the source

10 Nov 2025, 15:24 UTC

Source last checked

26 Oct 2026, 16:41 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-j346-h5wc-rw2m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2018-11802

Advisory: Incorrect Authorization in Apache Solr
IDs: CVE-2018-11802, GHSA-j346-h5wc-rw2m
Record: https://patchnext.com/advisories/cve-2018-11802 (revision 1, source checked 26 Oct 2026, 16:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.solr:solr-parent 7.7.0, 6.6.6; org.apache.solr:solr-core 7.7.0, 6.6.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.solr:solr-parent: affected >= 7.0.0, < 7.7.0; < 6.6.6; fixed in 7.7.0, 6.6.6
- Maven org.apache.solr:solr-core: affected >= 7.0.0, < 7.7.0; < 6.6.6; fixed in 7.7.0, 6.6.6

## Suggested inspection (read-only)
- Maven org.apache.solr:solr-parent: check the installed version with your package manager.
- Maven org.apache.solr:solr-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.solr:solr-parent, org.apache.solr:solr-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j346-h5wc-rw2m (GitHub-reviewed advisory GHSA-j346-h5wc-rw2m lists affected ranges: Maven org.apache.solr:solr-parent >=7.0.0 =0 =7.0.0 =0 <6.6.6)

Commands are suggestions: review each one before running it.