https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 09:43:11 +0000 https://cve.radiocsirt.org/vuln/bit-solr-2026-22444 <p><strong>Affected:</strong> Bitnami: solr</p> <p>The &#34;create core&#34; 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&#39;s &#34;allowPaths&#34; 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 &#34;user&#34; hashes.</p> <p>Solr deployments are subject to this vulnerability if they meet the following criteria: * Solr is running in its &#34;standalone&#34; mode. * Solr&#39;s &#34;allowPath&#34; setting is being used to restrict file access to certain directories. * Solr&#39;s &#34;create core&#34; API is exposed and accessible to untrusted users.  This can happen if Solr&#39;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 &#34;core-admin-edit&#34; predefined permission (or an equivalent custom permission) is given to low-trust (i.e. non-admin) user roles.</p> <p>Users can mitigate this by enabling Solr&#39;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…</p> <p><strong>Affected:</strong> Bitnami: solr</p> <p>The &#34;create core&#34; 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&#39;s &#34;allowPaths&#34; 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 &#34;user&#34; hashes.</p> <p>Solr deployments are subject to this vulnerability if they meet the following criteria: * Solr is running in its &#34;standalone&#34; mode. * Solr&#39;s &#34;allowPath&#34; setting is being used to restrict file access to certain directories. * Solr&#39;s &#34;create core&#34; API is exposed and accessible to untrusted users.  This can happen if Solr&#39;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 &#34;core-admin-edit&#34; predefined permission (or an equivalent custom permission) is given to low-trust (i.e. non-admin) user roles.</p> <p>Users can mitigate this by enabling Solr&#39;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…</p> https://cve.radiocsirt.org/vuln/bit-solr-2026-22444 https://cve.radiocsirt.org/vuln/cleanstart-2026-cg99434 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: solr</p> <p>Multiple security vulnerabilities affect the solr package. These issues are resolved in later releases. See references for individual vulnerability details.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> CleanStart: solr</p> <p>Multiple security vulnerabilities affect the solr package. These issues are resolved in later releases. See references for individual vulnerability details.</p> https://cve.radiocsirt.org/vuln/cleanstart-2026-cg99434 https://cve.radiocsirt.org/vuln/euvd-2026-266176 EUVD-2026-266176 https://cve.radiocsirt.org/vuln/euvd-2026-266176 https://cve.radiocsirt.org/vuln/fkie_cve-2026-22444 <p>The &#34;create core&#34; 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&#39;s &#34;allowPaths&#34; 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 &#34;user&#34; hashes.</p> <p>Solr deployments are subject to this vulnerability if they meet the following criteria: * Solr is running in its &#34;standalone&#34; mode. * Solr&#39;s &#34;allowPath&#34; setting is being used to restrict file access to certain directories. * Solr&#39;s &#34;create core&#34; API is exposed and accessible to untrusted users.  This can happen if Solr&#39;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 &#34;core-admin-edit&#34; predefined permission (or an equivalent custom permission) is given to low-trust (i.e. non-admin) user roles.</p> <p>Users can mitigate this by enabling Solr&#39;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…</p> <p>The &#34;create core&#34; 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&#39;s &#34;allowPaths&#34; 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 &#34;user&#34; hashes.</p> <p>Solr deployments are subject to this vulnerability if they meet the following criteria: * Solr is running in its &#34;standalone&#34; mode. * Solr&#39;s &#34;allowPath&#34; setting is being used to restrict file access to certain directories. * Solr&#39;s &#34;create core&#34; API is exposed and accessible to untrusted users.  This can happen if Solr&#39;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 &#34;core-admin-edit&#34; predefined permission (or an equivalent custom permission) is given to low-trust (i.e. non-admin) user roles.</p> <p>Users can mitigate this by enabling Solr&#39;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…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-22444 https://cve.radiocsirt.org/vuln/ghsa-vc2w-4v3p-2mqw <p><strong>Affected:</strong> Maven: org.apache.solr:solr-core</p> <p>The &#34;create core&#34; 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&#39;s &#34;allowPaths&#34; 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 &#34;user&#34; hashes.</p> <p>Solr deployments are subject to this vulnerability if they meet the following criteria: * Solr is running in its &#34;standalone&#34; mode. * Solr&#39;s &#34;allowPath&#34; setting is being used to restrict file access to certain directories. * Solr&#39;s &#34;create core&#34; API is exposed and accessible to untrusted users.  This can happen if Solr&#39;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 &#34;core-admin-edit&#34; predefined permission (or an equivalent custom permission) is given to low-trust (i.e. non-admin) user roles.</p> <p>Users can mitigate this by enabling Solr&#39;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…</p> <p><strong>Affected:</strong> Maven: org.apache.solr:solr-core</p> <p>The &#34;create core&#34; 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&#39;s &#34;allowPaths&#34; 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 &#34;user&#34; hashes.</p> <p>Solr deployments are subject to this vulnerability if they meet the following criteria: * Solr is running in its &#34;standalone&#34; mode. * Solr&#39;s &#34;allowPath&#34; setting is being used to restrict file access to certain directories. * Solr&#39;s &#34;create core&#34; API is exposed and accessible to untrusted users.  This can happen if Solr&#39;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 &#34;core-admin-edit&#34; predefined permission (or an equivalent custom permission) is given to low-trust (i.e. non-admin) user roles.</p> <p>Users can mitigate this by enabling Solr&#39;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…</p> https://cve.radiocsirt.org/vuln/ghsa-vc2w-4v3p-2mqw https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-22444 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: lucene-solr, Ubuntu:Pro:16.04:LTS: lucene-solr, Ubuntu:Pro:18.04:LTS: lucene-solr, Ubuntu:20.04:LTS: lucene-solr, Ubuntu:22.04:LTS: lucene-solr, Ubuntu:24.04:LTS: lucene-solr, Ubuntu:25.10: lucene-solr, Ubuntu:26.04:LTS: lucene-solr</p> <p>The &#34;create core&#34; 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&#39;s &#34;allowPaths&#34; 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 &#34;user&#34; hashes. Solr deployments are subject to this vulnerability if they meet the following criteria: * Solr is running in its &#34;standalone&#34; mode. * Solr&#39;s &#34;allowPath&#34; setting is being used to restrict file access to certain directories. * Solr&#39;s &#34;create core&#34; API is exposed and accessible to untrusted users.  This can happen if Solr&#39;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 &#34;core-admin-edit&#34; 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&#39;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 con…</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: lucene-solr, Ubuntu:Pro:16.04:LTS: lucene-solr, Ubuntu:Pro:18.04:LTS: lucene-solr, Ubuntu:20.04:LTS: lucene-solr, Ubuntu:22.04:LTS: lucene-solr, Ubuntu:24.04:LTS: lucene-solr, Ubuntu:25.10: lucene-solr, Ubuntu:26.04:LTS: lucene-solr</p> <p>The &#34;create core&#34; 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&#39;s &#34;allowPaths&#34; 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 &#34;user&#34; hashes. Solr deployments are subject to this vulnerability if they meet the following criteria: * Solr is running in its &#34;standalone&#34; mode. * Solr&#39;s &#34;allowPath&#34; setting is being used to restrict file access to certain directories. * Solr&#39;s &#34;create core&#34; API is exposed and accessible to untrusted users.  This can happen if Solr&#39;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 &#34;core-admin-edit&#34; 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&#39;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 con…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-22444 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0182 <p>Ein Angreifer kann mehrere Schwachstellen in Apache Solr ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren und vertrauliche Informationen offenzulegen.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Apache Solr ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren und vertrauliche Informationen offenzulegen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0182