# Incorrect Authorization in Apache Solr

Advisory record · `GHSA-j346-h5wc-rw2m`

- **Identifiers:** `GHSA-j346-h5wc-rw2m` · `CVE-2018-11802`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 9 Feb 2022
- **Updated:** 10 Nov 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Feb 2022, 23:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.solr:solr-parent` (Maven): affected `>=7.0.0, <7.7.0 || <6.6.6`; fixed in `7.7.0`, `6.6.6`
- `org.apache.solr:solr-core` (Maven): affected `>=7.0.0, <7.7.0 || <6.6.6`; fixed in `7.7.0`, `6.6.6`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Solr (solr-core and solr-parent, versions 7.0.0 up to 7.7.0 and 6.x before 6.6.6) can be affected in clusters that use the default RuleBasedAuthorizationPlugin. When a node receives a request for a collection it does not host, it proxies the request and skips authorization checks. Upgrade to Solr 7.7.0 or 6.6.6 or later.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.020, the 81st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-j346-h5wc-rw2m)

## Sources

- [GitHub Advisory Database: GHSA-j346-h5wc-rw2m](https://github.com/advisories/GHSA-j346-h5wc-rw2m)
- [OSV: GHSA-j346-h5wc-rw2m](https://osv.dev/vulnerability/GHSA-j346-h5wc-rw2m)
- <https://nvd.nist.gov/vuln/detail/CVE-2018-11802>
- <https://github.com/apache/lucene-solr/commit/add003f217806afb4e1604f697cdb0a5a7115895>
- <https://github.com/apache/lucene-solr>
- <https://issues.apache.org/jira/browse/SOLR-12514>
- <https://www.openwall.com/lists/oss-security/2019/04/24/1>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-j346-h5wc-rw2m>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-j346-h5wc-rw2m/>. Everything for agents: <https://agentprime.io/llms.txt>.
