<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 19:06:55 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-04325</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-04325</link>
      <description>bdu:2025-04325</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-04325</guid>
    </item>
    <item>
      <title>BIT-solr-2025-24814 — Apache Solr: Core-creation with "trusted" configset can use arbitrary untrusted files</title>
      <link>https://cve.radiocsirt.org/vuln/bit-solr-2025-24814</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: solr&lt;/p&gt;
&lt;p&gt;Core creation allows users to replace &amp;#34;trusted&amp;#34; configset files with arbitrary configuration&lt;/p&gt;
&lt;p&gt;Solr instances that (1) use the &amp;#34;FileSystemConfigSetService&amp;#34; component (the default in &amp;#34;standalone&amp;#34; or &amp;#34;user-managed&amp;#34; mode), and (2) are running without authentication and authorization are vulnerable to a sort of privilege escalation wherein individual &amp;#34;trusted&amp;#34; configset files can be ignored in favor of potentially-untrusted replacements available elsewhere on the filesystem.  These replacement config files are treated as &amp;#34;trusted&amp;#34; and can use &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags to add to Solr&amp;#39;s classpath, which an attacker might use to load malicious code as a searchComponent or other plugin.&lt;/p&gt;
&lt;p&gt;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 &amp;#34;FileSystemConfigSetService&amp;#34;).  Users are also recommended to upgrade to Solr 9.8.0, which mitigates this issue by disabling use of &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags by default.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: solr&lt;/p&gt;
&lt;p&gt;Core creation allows users to replace &amp;#34;trusted&amp;#34; configset files with arbitrary configuration&lt;/p&gt;
&lt;p&gt;Solr instances that (1) use the &amp;#34;FileSystemConfigSetService&amp;#34; component (the default in &amp;#34;standalone&amp;#34; or &amp;#34;user-managed&amp;#34; mode), and (2) are running without authentication and authorization are vulnerable to a sort of privilege escalation wherein individual &amp;#34;trusted&amp;#34; configset files can be ignored in favor of potentially-untrusted replacements available elsewhere on the filesystem.  These replacement config files are treated as &amp;#34;trusted&amp;#34; and can use &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags to add to Solr&amp;#39;s classpath, which an attacker might use to load malicious code as a searchComponent or other plugin.&lt;/p&gt;
&lt;p&gt;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 &amp;#34;FileSystemConfigSetService&amp;#34;).  Users are also recommended to upgrade to Solr 9.8.0, which mitigates this issue by disabling use of &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags by default.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-solr-2025-24814</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0556 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0556</link>
      <description>certfr-2026-avi-0556</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0556</guid>
    </item>
    <item>
      <title>EUVD-2026-217790</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-217790</link>
      <description>EUVD-2026-217790</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-217790</guid>
    </item>
    <item>
      <title>fkie_cve-2025-24814</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-24814</link>
      <description>&lt;p&gt;Core creation allows users to replace &amp;#34;trusted&amp;#34; configset files with arbitrary configuration&lt;/p&gt;
&lt;p&gt;Solr instances that (1) use the &amp;#34;FileSystemConfigSetService&amp;#34; component (the default in &amp;#34;standalone&amp;#34; or &amp;#34;user-managed&amp;#34; mode), and (2) are running without authentication and authorization are vulnerable to a sort of privilege escalation wherein individual &amp;#34;trusted&amp;#34; configset files can be ignored in favor of potentially-untrusted replacements available elsewhere on the filesystem.  These replacement config files are treated as &amp;#34;trusted&amp;#34; and can use &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags to add to Solr&amp;#39;s classpath, which an attacker might use to load malicious code as a searchComponent or other plugin.&lt;/p&gt;
&lt;p&gt;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 &amp;#34;FileSystemConfigSetService&amp;#34;).  Users are also recommended to upgrade to Solr 9.8.0, which mitigates this issue by disabling use of &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags by default.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Core creation allows users to replace &amp;#34;trusted&amp;#34; configset files with arbitrary configuration&lt;/p&gt;
&lt;p&gt;Solr instances that (1) use the &amp;#34;FileSystemConfigSetService&amp;#34; component (the default in &amp;#34;standalone&amp;#34; or &amp;#34;user-managed&amp;#34; mode), and (2) are running without authentication and authorization are vulnerable to a sort of privilege escalation wherein individual &amp;#34;trusted&amp;#34; configset files can be ignored in favor of potentially-untrusted replacements available elsewhere on the filesystem.  These replacement config files are treated as &amp;#34;trusted&amp;#34; and can use &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags to add to Solr&amp;#39;s classpath, which an attacker might use to load malicious code as a searchComponent or other plugin.&lt;/p&gt;
&lt;p&gt;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 &amp;#34;FileSystemConfigSetService&amp;#34;).  Users are also recommended to upgrade to Solr 9.8.0, which mitigates this issue by disabling use of &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags by default.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-24814</guid>
    </item>
    <item>
      <title>GHSA-68r2-fwcg-qpm8 — Apache Solr vulnerable to Execution with Unnecessary Privileges</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-68r2-fwcg-qpm8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.solr:solr-core&lt;/p&gt;
&lt;p&gt;Core creation allows users to replace &amp;#34;trusted&amp;#34; configset files with arbitrary configuration&lt;/p&gt;
&lt;p&gt;Solr instances that (1) use the &amp;#34;FileSystemConfigSetService&amp;#34; component (the default in &amp;#34;standalone&amp;#34; or &amp;#34;user-managed&amp;#34; mode), and (2) are running without authentication and authorization are vulnerable to a sort of privilege escalation wherein individual &amp;#34;trusted&amp;#34; configset files can be ignored in favor of potentially-untrusted replacements available elsewhere on the filesystem.  These replacement config files are treated as &amp;#34;trusted&amp;#34; and can use &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags to add to Solr&amp;#39;s classpath, which an attacker might use to load malicious code as a searchComponent or other plugin.&lt;/p&gt;
&lt;p&gt;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 &amp;#34;FileSystemConfigSetService&amp;#34;).  Users are also recommended to upgrade to Solr 9.8.0, which mitigates this issue by disabling use of &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags by default.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.apache.solr:solr-core&lt;/p&gt;
&lt;p&gt;Core creation allows users to replace &amp;#34;trusted&amp;#34; configset files with arbitrary configuration&lt;/p&gt;
&lt;p&gt;Solr instances that (1) use the &amp;#34;FileSystemConfigSetService&amp;#34; component (the default in &amp;#34;standalone&amp;#34; or &amp;#34;user-managed&amp;#34; mode), and (2) are running without authentication and authorization are vulnerable to a sort of privilege escalation wherein individual &amp;#34;trusted&amp;#34; configset files can be ignored in favor of potentially-untrusted replacements available elsewhere on the filesystem.  These replacement config files are treated as &amp;#34;trusted&amp;#34; and can use &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags to add to Solr&amp;#39;s classpath, which an attacker might use to load malicious code as a searchComponent or other plugin.&lt;/p&gt;
&lt;p&gt;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 &amp;#34;FileSystemConfigSetService&amp;#34;).  Users are also recommended to upgrade to Solr 9.8.0, which mitigates this issue by disabling use of &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags by default.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-68r2-fwcg-qpm8</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-24814</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-24814</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;Core creation allows users to replace &amp;#34;trusted&amp;#34; configset files with arbitrary configuration Solr instances that (1) use the &amp;#34;FileSystemConfigSetService&amp;#34; component (the default in &amp;#34;standalone&amp;#34; or &amp;#34;user-managed&amp;#34; mode), and (2) are running without authentication and authorization are vulnerable to a sort of privilege escalation wherein individual &amp;#34;trusted&amp;#34; configset files can be ignored in favor of potentially-untrusted replacements available elsewhere on the filesystem.  These replacement config files are treated as &amp;#34;trusted&amp;#34; and can use &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags to add to Solr&amp;#39;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 &amp;#34;FileSystemConfigSetService&amp;#34;).  Users are also recommended to upgrade to Solr 9.8.0, which mitigates this issue by disabling use of &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags by default.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;Core creation allows users to replace &amp;#34;trusted&amp;#34; configset files with arbitrary configuration Solr instances that (1) use the &amp;#34;FileSystemConfigSetService&amp;#34; component (the default in &amp;#34;standalone&amp;#34; or &amp;#34;user-managed&amp;#34; mode), and (2) are running without authentication and authorization are vulnerable to a sort of privilege escalation wherein individual &amp;#34;trusted&amp;#34; configset files can be ignored in favor of potentially-untrusted replacements available elsewhere on the filesystem.  These replacement config files are treated as &amp;#34;trusted&amp;#34; and can use &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags to add to Solr&amp;#39;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 &amp;#34;FileSystemConfigSetService&amp;#34;).  Users are also recommended to upgrade to Solr 9.8.0, which mitigates this issue by disabling use of &amp;#34;&amp;lt;lib&amp;gt;&amp;#34; tags by default.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-24814</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0197 — Apache Solr: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0197</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Apache Solr ausnutzen, um Dateien zu manipulieren oder seine Rechte zu erweitern.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Apache Solr ausnutzen, um Dateien zu manipulieren oder seine Rechte zu erweitern.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0197</guid>
    </item>
  </channel>
</rss>
