<?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 20:40:00 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-245023</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-245023</link>
      <description>EUVD-2026-245023</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-245023</guid>
    </item>
    <item>
      <title>fkie_cve-2024-24824</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-24824</link>
      <description>&lt;p&gt;Graylog is a free and open log management platform. Starting in version 2.0.0 and prior to versions 5.1.11 and 5.2.4, arbitrary classes can be loaded and instantiated using a HTTP PUT request to the `/api/system/cluster_config/` endpoint. Graylog&amp;#39;s cluster config system uses fully qualified class names as config keys. To validate the existence of the requested class before using them, Graylog loads the class using the class loader. If a user with the appropriate permissions performs the request, arbitrary classes with 1-arg String constructors can be instantiated. This will execute arbitrary code that is run during class instantiation. In the specific use case of `java.io.File`, the behavior of the internal web-server stack will lead to information exposure by including the entire file content in the response to the REST request. Versions 5.1.11 and 5.2.4 contain a fix for this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Graylog is a free and open log management platform. Starting in version 2.0.0 and prior to versions 5.1.11 and 5.2.4, arbitrary classes can be loaded and instantiated using a HTTP PUT request to the `/api/system/cluster_config/` endpoint. Graylog&amp;#39;s cluster config system uses fully qualified class names as config keys. To validate the existence of the requested class before using them, Graylog loads the class using the class loader. If a user with the appropriate permissions performs the request, arbitrary classes with 1-arg String constructors can be instantiated. This will execute arbitrary code that is run during class instantiation. In the specific use case of `java.io.File`, the behavior of the internal web-server stack will lead to information exposure by including the entire file content in the response to the REST request. Versions 5.1.11 and 5.2.4 contain a fix for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-24824</guid>
    </item>
    <item>
      <title>GHSA-p6gg-5hf4-4rgj — Graylog vulnerable to instantiation of arbitrary classes triggered by API request</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p6gg-5hf4-4rgj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.graylog2:graylog2-server&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Arbitrary classes can be loaded and instantiated using a HTTP PUT request to the `/api/system/cluster_config/` endpoint.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Graylog&amp;#39;s cluster config system uses fully qualified class names as config keys. To validate the existence of the requested class before using them, Graylog loads the class using the class loader.&lt;/p&gt;
&lt;p&gt;https://github.com/Graylog2/graylog2-server/blob/e458db8bf4f789d4d19f1b37f0263f910c8d036c/graylog2-server/src/main/java/org/graylog2/rest/resources/system/ClusterConfigResource.java#L208-L214&lt;/p&gt;
&lt;p&gt;### PoC
A request of the following form will output the content of the `/etc/passwd` file:&lt;/p&gt;
&lt;p&gt;```
curl -u admin:&amp;lt;admin-password&amp;gt; -X PUT http://localhost:9000/api/system/cluster_config/java.io.File \
    -H &amp;#34;Content-Type: application/json&amp;#34; \
    -H &amp;#34;X-Requested-By: poc&amp;#34; \
    -d &amp;#39;&amp;#34;/etc/passwd&amp;#34;&amp;#39;
```&lt;/p&gt;
&lt;p&gt;To perform the request, authorization is required. Only users posessing the `clusterconfigentry:create` and `clusterconfigentry:edit` permissions are allowed to do so. These permissions are usually only granted to `Admin` users.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;If a user with the appropriate permissions performs the request, arbitrary classes with 1-arg String constructors can be instantiated.&lt;/p&gt;
&lt;p&gt;This will execute arbitrary code that is run during class instantiation.&lt;/p&gt;
&lt;p&gt;In the specific use case of `java.io.File`, the behaviour of the internal web-server stack will lead to information exposure by including the entire file content in the response to the REST request.&lt;/p&gt;
&lt;p&gt;### Cre…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.graylog2:graylog2-server&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Arbitrary classes can be loaded and instantiated using a HTTP PUT request to the `/api/system/cluster_config/` endpoint.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Graylog&amp;#39;s cluster config system uses fully qualified class names as config keys. To validate the existence of the requested class before using them, Graylog loads the class using the class loader.&lt;/p&gt;
&lt;p&gt;https://github.com/Graylog2/graylog2-server/blob/e458db8bf4f789d4d19f1b37f0263f910c8d036c/graylog2-server/src/main/java/org/graylog2/rest/resources/system/ClusterConfigResource.java#L208-L214&lt;/p&gt;
&lt;p&gt;### PoC
A request of the following form will output the content of the `/etc/passwd` file:&lt;/p&gt;
&lt;p&gt;```
curl -u admin:&amp;lt;admin-password&amp;gt; -X PUT http://localhost:9000/api/system/cluster_config/java.io.File \
    -H &amp;#34;Content-Type: application/json&amp;#34; \
    -H &amp;#34;X-Requested-By: poc&amp;#34; \
    -d &amp;#39;&amp;#34;/etc/passwd&amp;#34;&amp;#39;
```&lt;/p&gt;
&lt;p&gt;To perform the request, authorization is required. Only users posessing the `clusterconfigentry:create` and `clusterconfigentry:edit` permissions are allowed to do so. These permissions are usually only granted to `Admin` users.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;If a user with the appropriate permissions performs the request, arbitrary classes with 1-arg String constructors can be instantiated.&lt;/p&gt;
&lt;p&gt;This will execute arbitrary code that is run during class instantiation.&lt;/p&gt;
&lt;p&gt;In the specific use case of `java.io.File`, the behaviour of the internal web-server stack will lead to information exposure by including the entire file content in the response to the REST request.&lt;/p&gt;
&lt;p&gt;### Cre…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p6gg-5hf4-4rgj</guid>
    </item>
    <item>
      <title>gsd-2024-24824</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-24824</link>
      <description>gsd-2024-24824</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-24824</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0316 — Graylog: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0316</link>
      <description>&lt;p&gt;Ein entfernter authentifizierter Angreifer kann mehrere Schwachstellen in Graylog ausnutzen, um seine Privilegien zu erhöhen oder beliebigen Code auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter authentifizierter Angreifer kann mehrere Schwachstellen in Graylog ausnutzen, um seine Privilegien zu erhöhen oder beliebigen Code auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0316</guid>
    </item>
  </channel>
</rss>
