Update solr.version to v9.10.1

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.apache.solr:solr-analysis-extras (source)	9.4.1 → 9.10.1
org.apache.solr:solr-core (source)	9.4.1 → 9.10.1
org.apache.solr:solr-solrj (source)	9.4.1 → 9.10.1
org.apache.solr:solr-api (source)	9.4.1 → 9.10.1

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Apache Solr Relative Path Traversal vulnerability

CVE-2024-52012 / GHSA-4p5m-gvpf-f3x5

More information

Details

Relative Path Traversal vulnerability in Apache Solr.

Solr instances running on Windows are vulnerable to arbitrary filepath write-access, due to a lack of input-sanitation in the "configset upload" API.  Commonly known as a "zipslip", maliciously constructed ZIP files can use relative filepaths to write data to unanticipated parts of the filesystem.  
This issue affects Apache Solr: from 6.6 through 9.7.0.

Users are recommended to upgrade to version 9.8.0, which fixes the issue.  Users unable to upgrade may also safely prevent the issue by using Solr's "Rule-Based Authentication Plugin" to restrict access to the configset upload API, so that it can only be accessed by a trusted set of administrators/users.

Severity

• CVSS Score: 6.6 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U

References

• https://nvd.nist.gov/vuln/detail/CVE-2024-52012
• https://lists.apache.org/thread/yp39pgbv4vf1746pf5yblz84lv30vfxd
• http://www.openwall.com/lists/oss-security/2025/01/26/2
• https://github.com/apache/solr/commit/5795edd143b8fcb2ffaf7f278a099b8678adf396
• https://issues.apache.org/jira/browse/SOLR-17543
• https://github.com/advisories/GHSA-4p5m-gvpf-f3x5

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Apache Solr vulnerable to Execution with Unnecessary Privileges

CVE-2025-24814 / GHSA-68r2-fwcg-qpm8

More information

Details

Core creation allows users to replace "trusted" configset files with arbitrary configuration

Solr instances that (1) use the "FileSystemConfigSetService" component (the default in "standalone" or "user-managed" mode), and (2) are running without authentication and authorization are vulnerable to a sort of privilege escalation wherein individual "trusted" configset files can be ignored in favor of potentially-untrusted replacements available elsewhere on the filesystem.  These replacement config files are treated as "trusted" and can use "" tags to add to Solr's classpath, which an attacker might use to load malicious code as a searchComponent or other plugin.

This issue affects all Apache Solr versions up through Solr 9.7.  Users can protect against the vulnerability by enabling authentication and authorization on their Solr clusters or switching to SolrCloud (and away from "FileSystemConfigSetService").  Users are also recommended to upgrade to Solr 9.8.0, which mitigates this issue by disabling use of "" tags by default.

Severity

• CVSS Score: 7.2 / 10 (High)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U

References

• https://nvd.nist.gov/vuln/detail/CVE-2025-24814
• https://lists.apache.org/thread/gl291pn8x9f9n52ys5l0pc0b6qtf0qw1
• http://www.openwall.com/lists/oss-security/2025/01/26/1
• https://github.com/apache/solr/commit/f492e24881c5724a1b1baecfc9549e2cb0257525
• https://issues.apache.org/jira/browse/SOLR-16781
• https://security.netapp.com/advisory/ntap-20250214-0002
• https://github.com/advisories/GHSA-68r2-fwcg-qpm8

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Apache Solr: Unauthorized bypass of certain "predefined permission" rules in the RuleBasedAuthorizationPlugin

CVE-2026-22022 / GHSA-qr3p-2xj2-q7hq

More information

Details

Deployments 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.

Severity

• CVSS Score: 8.2 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N

References

• https://nvd.nist.gov/vuln/detail/CVE-2026-22022
• https://lists.apache.org/thread/d59hqbgo7p62myq7mgfpz7or8n1j7wbn
• http://www.openwall.com/lists/oss-security/2026/01/20/4
• https://github.com/apache/solr/commit/c135e6335c7158fa26e96b0dc386f825255b47c0
• https://issues.apache.org/jira/browse/SOLR-18054
• https://github.com/advisories/GHSA-qr3p-2xj2-q7hq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

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

CVE-2026-22444 / GHSA-vc2w-4v3p-2mqw

More information

Details

The "create core" API of Apache Solr 8.6 through 9.10.0 lacks sufficient input validation on some API parameters, which can cause Solr to check the existence of and attempt to read file-system paths that should be disallowed by Solr's "allowPaths" security setting https://https://solr.apache.org/guide/solr/latest/configuration-guide/configuring-solr-xml.html#the-solr-element .  These read-only accesses can allow users to create cores using unexpected configsets if any are accessible via the filesystem.  On Windows systems configured to allow UNC paths this can additionally cause disclosure of NTLM "user" hashes. 

Solr deployments are subject to this vulnerability if they meet the following criteria:

• Solr is running in its "standalone" mode.
• Solr's "allowPath" setting is being used to restrict file access to certain directories.
• Solr's "create core" API is exposed and accessible to untrusted users.  This can happen if Solr's RuleBasedAuthorizationPlugin https://solr.apache.org/guide/solr/latest/deployment-guide/rule-based-authorization-plugin.html is disabled, or if it is enabled but the "core-admin-edit" predefined permission (or an equivalent custom permission) is given to low-trust (i.e. non-admin) user roles.

Users can mitigate this by enabling Solr's RuleBasedAuthorizationPlugin (if disabled) and configuring a permission-list that prevents untrusted users from creating new Solr cores.  Users should also upgrade to Apache Solr 9.10.1 or greater, which contain fixes for this issue.

Severity

• CVSS Score: 7.1 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

References

• https://nvd.nist.gov/vuln/detail/CVE-2026-22444
• https://lists.apache.org/thread/qkrb9dd4xrlqmmq73lrhkbfkttto2d1m
• http://www.openwall.com/lists/oss-security/2026/01/20/5
• https://issues.apache.org/jira/browse/SOLR-18058
• https://github.com/advisories/GHSA-vc2w-4v3p-2mqw

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	maven/​org.apache.solr/​solr-solrj@​9.4.1 ⏵ 9.10.1					-20
	maven/​org.apache.solr/​solr-core@​9.4.1 ⏵ 9.10.1		+25			-20
	maven/​org.apache.solr/​solr-analysis-extras@​9.4.1 ⏵ 9.10.1	+1		-10		-30

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: maven com.fasterxml.jackson.core:jackson-databind is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pom.xml → maven/org.apache.solr/solr-core@9.10.1 → maven/com.fasterxml.jackson.core/jackson-databind@2.18.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/com.fasterxml.jackson.core/jackson-databind@2.18.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: maven com.fasterxml.jackson.core:jackson-databind is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pom.xml → maven/org.apache.solr/solr-core@9.10.1 → maven/com.fasterxml.jackson.core/jackson-databind@2.18.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/com.fasterxml.jackson.core/jackson-databind@2.18.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: maven com.fasterxml.woodstox:woodstox-core is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pom.xml → maven/org.apache.solr/solr-core@9.10.1 → maven/com.fasterxml.woodstox/woodstox-core@7.0.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/com.fasterxml.woodstox/woodstox-core@7.0.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: maven com.google.guava:guava is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pom.xml → maven/org.apache.solr/solr-core@9.10.1 → maven/com.google.guava/guava@33.1.0-jre ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/com.google.guava/guava@33.1.0-jre. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: maven com.google.guava:guava is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pom.xml → maven/org.apache.solr/solr-core@9.10.1 → maven/com.google.guava/guava@33.1.0-jre ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/com.google.guava/guava@33.1.0-jre. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: maven commons-codec:commons-codec is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pom.xml → maven/org.apache.solr/solr-core@9.10.1 → maven/commons-codec/commons-codec@1.19.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/commons-codec/commons-codec@1.19.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report