SolrApplication · Apache
CVE-2026-22022
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDeployments of Apache Solr 5.3.0 through 9.10.0 that rely on Solr's "Rule Based Authorization Plugin" are vulnerable to allowing unauthorized access to certain Solr APIs, due to insufficiently strict input validation in those components. Only deployments that meet all of the following criteria are impacted by this vulnerability: * Use of Solr's "RuleBasedAuthorizationPlugin" * A RuleBasedAuthorizationPlugin config (see security.json) that specifies multiple "roles" * A RuleBasedAuthorizationPlugin permission list (see security.json) that uses one or more of the following pre-defined permission rules: "config-read", "config-edit", "schema-read", "metrics-read", or "security-read". * A RuleBasedAuthorizationPlugin permission list that doesn't define the "all" pre-defined permission * A networking setup that allows clients to make unfiltered network requests to Solr. (i.e. user-submitted HTTP/HTTPS requests reach Solr as-is, unmodified or restricted by any intervening proxy or gateway) Users can mitigate this vulnerability by ensuring that their RuleBasedAuthorizationPlugin configuration specifies the "all" pre-defined permission and associates the permission with an "admin" or other privileged role. Users can also upgrade to a Solr version outside of the impacted range, such as the recently released Solr 9.10.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Solr's RuleBasedAuthorizationPlugin has insufficient input validation that allows unauthorized access to sensitive APIs (config-read, config-edit, schema-read, metrics-read, security-read) when the 'all' pre-defined permission is not defined in security.json, enabling attackers to bypass authorization checks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SolrApplication
>= 5.3.0, < 9.10.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Solr installation and versionRun 'solr -v' or check the version via the Solr admin UI, or locate the solr.jar file and inspect its version manifestAffected if Installed version is 5.3.0 through 9.10.0 (inclusive)
-
Locate the security.json configuration fileFind the security.json file in the Solr configuration directory (typically in solr/security/ or the conf directory of your Solr home)Affected if security.json exists in the Solr configuration path
-
Verify if the 'all' permission is definedOpen security.json and search for an 'all' permission entry within the permissions array. Look for a permission block containing 'name': 'all'Affected if The 'all' permission is NOT defined or is missing from the permissions array in security.json
-
Confirm authorization plugin in useCheck security.json for the 'authorization' section and verify 'class' is set to RuleBasedAuthorizationPlugin or solr.RuleBasedAuthorizationPluginAffected if RuleBasedAuthorizationPlugin is configured as the authorization class
You are affected if Solr version is 9.10.0 or earlier AND RuleBasedAuthorizationPlugin is in use AND the 'all' permission is not defined in security.json, allowing unauthorized access to sensitive APIs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.10.1
Add the 'all' pre-defined permission to the RuleBasedAuthorizationPlugin configuration (security.json) and associate it with an admin or privileged role, or upgrade to Solr 9.10.1 or later.
Solr 9.10.1
- 1. Back up your current Solr configuration (particularly security.json) and all data
- 2. Download Solr 9.10.1 from the official Apache Solr download page (https://solr.apache.org/downloads.html)
- 3. Stop the currently running Solr instance
- 4. Install or extract Solr 9.10.1 to your target directory
- 5. Restore your Solr configuration files from the backup
- 6. Start Solr 9.10.1 and verify the service is running
- 7. Test that the RuleBasedAuthorizationPlugin is functioning correctly with the new version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Solr
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22022 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22022 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data