# Apache Solr: Insufficient file-access checking in standalone core-creation requests

Advisory record · `GHSA-vc2w-4v3p-2mqw`

- **Identifiers:** `GHSA-vc2w-4v3p-2mqw` · `BIT-solr-2026-22444` · `CVE-2026-22444`
- **State:** Confirmed
- **Severity:** CVSS 7.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html)
- **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 21 Jan 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Jan 2026, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.solr:solr-core` (Maven): affected `>=8.6.0, <9.10.1`; fixed in `9.10.1`

## Machine-written summary

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

> Apache Solr (org.apache.solr:solr-core, versions 8.6.0 through 9.10.0) is vulnerable in standalone mode when the allowPaths setting restricts file access. The create core API does not validate some parameters, so an attacker who can reach it can make Solr check and read file-system paths that allowPaths should block, and create cores from accessible configsets. On Windows systems that allow UNC paths, this can also disclose NTLM user hashes. Upgrade to version 9.10.1 or later. Until then, enable the RuleBasedAuthorizationPlugin and block untrusted users from the core-admin-edit permission.

Written 2 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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0069, the 53rd percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:17 UTC: First seen by agentprime
- 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vc2w-4v3p-2mqw)

## Sources

- [GitHub Advisory Database: GHSA-vc2w-4v3p-2mqw](https://github.com/advisories/GHSA-vc2w-4v3p-2mqw)
- [OSV: GHSA-vc2w-4v3p-2mqw](https://osv.dev/vulnerability/GHSA-vc2w-4v3p-2mqw)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-22444>
- <https://github.com/apache/solr>
- <https://issues.apache.org/jira/browse/SOLR-18058>
- <https://lists.apache.org/thread/qkrb9dd4xrlqmmq73lrhkbfkttto2d1m>
- <http://www.openwall.com/lists/oss-security/2026/01/20/5>

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-vc2w-4v3p-2mqw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vc2w-4v3p-2mqw/>. Everything for agents: <https://agentprime.io/llms.txt>.