# Apache Solr: Backup/Restore APIs allow for deployment of executables in malicious ConfigSets Advisory record · `GHSA-37vr-vmg4-jwpw` - **Identifiers:** `GHSA-37vr-vmg4-jwpw` · `BIT-solr-2023-50386` · `CVE-2023-50386` - **State:** Confirmed - **Severity:** CVSS 8.8 High - **Critical:** Yes: CVSS 7+ and EPSS - **Weakness (CWE):** [CWE-434](https://cwe.mitre.org/data/definitions/434.html) · [CWE-913](https://cwe.mitre.org/data/definitions/913.html) - **Tags:** [Unrestricted file upload](https://agentprime.io/advisories/tag/file-upload.md) · [CWE-913](https://agentprime.io/advisories/tag/cwe-913.md) - **Published:** 9 Feb 2024 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 9 Feb 2024, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 8.8 (7.0 or more) and EPSS 0.84 (0.1 or more): a high score and a real chance of exploitation in the next 30 days. How we decide what’s critical: ## Affected packages - `org.apache.solr:solr-core` (Maven): affected `>=6.0.0, <8.11.3 || >=9.0.0, <9.4.1`; fixed in `8.11.3`, `9.4.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Apache Solr versions 6.0.0 through 8.11.2 and 9.0.0 before 9.4.1 are vulnerable. Solr ConfigSets accepted uploaded Java jar and class files, and when a collection was backed up to a directory on Solr's classpath, those files could be loaded for any ConfigSet. With authorization enabled, the impact is limited to users who already hold Backup permissions and can add libraries; the source does not say what an attacker can do without authorization. Upgrade to Solr 8.11.3 or 9.4.1, which fix the issue. 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 - 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.84, the 99th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:18 UTC: First seen by agentprime - 31 Oct 2026, 14:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-37vr-vmg4-jwpw) ## Sources - [GitHub Advisory Database: GHSA-37vr-vmg4-jwpw](https://github.com/advisories/GHSA-37vr-vmg4-jwpw) - [OSV: GHSA-37vr-vmg4-jwpw](https://osv.dev/vulnerability/GHSA-37vr-vmg4-jwpw) - - - - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .