CVE-2018-11802: In Apache Solr, the cluster can be partitioned into multiple collections and only a subset of nodes actually host any given collection.
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2% (FIRST EPSS); higher than 81.2% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: org.apache.solr:solr-core (Maven) 7.7.0, 6.6.6; org.apache.solr:solr-parent (Maven) 7.7.0, 6.6.6.
Low priority for now. Upgrade to org.apache.solr:solr-core (Maven) 7.7.0, 6.6.6; org.apache.solr:solr-parent (Maven) 7.7.0, 6.6.6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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 7.7 that use the default authorization mechanism of Solr (RuleBasedAuthorizationPlugin).
- Published
- Apr 1, 2020
- Updated
- Jun 16, 2026
- EPSS
- 2.0% · 81th percentile
- CWE
- CWE-863
Report tools
Action score
18
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| apache | solr | cpe:2.3:a:apache:solr |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.
Apache Apache Solr
- before 7.7affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache solr4.2.0 and later · before 6.6.6
- apache solr7.0.0 and later · before 7.7.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.apache.solr:solr-core | from 7.0.0 · before 7.7.0 | 7.7.0 |
| Maven | org.apache.solr:solr-core | before 6.6.6 | 6.6.6 |
| Maven | org.apache.solr:solr-parent | from 7.0.0 · before 7.7.0 | 7.7.0 |
| Maven | org.apache.solr:solr-parent | before 6.6.6 | 6.6.6 |
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-17558Apache Solr 5.0.0 to Apache Solr 8.3.1 are vulnerable to a Remote Code Execution through the VelocityResponseWriter.KEV90Now
- CVE-2019-0193In Apache Solr, the DataImportHandler, an optional but popular module to pull in data from databases and other sources, has a feature in…KEV83Now
- CVE-2024-45216Apache Solr: Authentication bypass possible using a fake URL Path ending67This week
Published before and after this one in the same product
- ← EarlierCVE-2019-12401Sep 10, 2019 · Solr versions 1.3.0 to 1.4.1, 3.1.0 to 3.6.2 and 4.0.0 to 4.10.4 are vulnerable to an XML resource consumption attack (a.k.a.33Monitor
- ← EarlierCVE-2019-12409Nov 18, 2019 · The 8.1.1 and 8.2.0 releases of Apache Solr contain an insecure setting for the ENABLE_REMOTE_JMX_OPTS configuration option in the default…45Plan
- Later →CVE-2020-13941Aug 17, 2020 · Reported in SOLR-14515 (private) and fixed in SOLR-14561 (public), released in Solr version 8.6.0.37Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.apache.solr:solr-core | 6.6.6 | Package registry (OSV) |
| Maven:org.apache.solr:solr-core | 7.7.0 | Package registry (OSV) |
| Maven:org.apache.solr:solr-parent | 6.6.6 | Package registry (OSV) |
| Maven:org.apache.solr:solr-parent | 7.7.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.